Prev: Fwd: [sudo-workers] sudo 1.7.3rc1 available
Next: [Medical package] - Presentation of FreeDiams: Free prescriber
From: Eitan Adler on 28 Jun 2010 22:57
Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
that the following code compiles and fails with the version of clang++
from ports?
This works with g++ and fails with clang++ for me.

Here is the original code
#include <iostream>
int main()
{
std::cout << 1;
return 1;
}

My bug report is here: http://llvm.org/bugs/show_bug.cgi?id=7489

I want to know if this is my problem or a clang++ problem or a bug
somewhere else.
--
Eitan Adler
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Boris Kochergin on 29 Jun 2010 00:36
Eitan Adler wrote:
> Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
> that the following code compiles and fails with the version of clang++
> from ports?
> This works with g++ and fails with clang++ for me.
>
> Here is the original code
> #include <iostream>
> int main()
> {
> std::cout << 1;
> return 1;
> }
>
> My bug report is here: http://llvm.org/bugs/show_bug.cgi?id=7489
>
> I want to know if this is my problem or a clang++ problem or a bug
> somewhere else.
>
Works fine here:

# uname -a
FreeBSD peer 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #2: Mon Feb 22
23:18:53 EST 2010 root(a)peer:/usr/obj/usr/src/sys/PEER i386

# clang++ -v
clang version 1.1 (branches/release_27)
Target: i386-portbld-freebsd8.0
Thread model: posix

I can try it on a recent CURRENT machine tomorrow, but perhaps you'd
best share your environment. I've compiled non-trivial C++ programs with
clang++ and they've behaved properly.

-Boris
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Boris Kochergin on 29 Jun 2010 00:41
Boris Kochergin wrote:
> Eitan Adler wrote:
>> Can anyone with FreeBSD 8.1-RC1 i386 or FreeBSD 8.1-RC2 i386 confirm
>> that the following code compiles and fails with the version of clang++
>> from ports?
>> This works with g++ and fails with clang++ for me.
>>
>> Here is the original code
>> #include <iostream>
>> int main()
>> {
>> std::cout << 1;
>> return 1;
>> }
>>
>> My bug report is here: http://llvm.org/bugs/show_bug.cgi?id=7489
>>
>> I want to know if this is my problem or a clang++ problem or a bug
>> somewhere else.
>>
> Works fine here:
>
> # uname -a
> FreeBSD peer 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #2: Mon Feb 22
> 23:18:53 EST 2010 root(a)peer:/usr/obj/usr/src/sys/PEER i386
>
> # clang++ -v
> clang version 1.1 (branches/release_27)
> Target: i386-portbld-freebsd8.0
> Thread model: posix
>
> I can try it on a recent CURRENT machine tomorrow, but perhaps you'd
> best share your environment. I've compiled non-trivial C++ programs
> with clang++ and they've behaved properly.
>
> -Boris
>
One difference I notice between your environment and mine is that,
according to your bug report, your program links against
/usr/local/lib/gcc46/libstdc++.so.6, while mine links against
/usr/lib/libstdc++.so.6.

-Boris
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Eitan Adler on 29 Jun 2010 09:44
>>> My bug report is here: http://llvm.org/bugs/show_bug.cgi?id=7489
>>>
>>> I want to know if this is my problem or a clang++ problem or a bug
>>> somewhere else.
>>>
>>
>> Works fine here:
>>
>> # uname -a
>> FreeBSD peer 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #2: Mon Feb 22 23:18:53
>> EST 2010     root(a)peer:/usr/obj/usr/src/sys/PEER  i386
>>
>> # clang++ -v
>> clang version 1.1 (branches/release_27)
>> Target: i386-portbld-freebsd8.0
>> Thread model: posix
>>
>> I can try it on a recent CURRENT machine tomorrow, but perhaps you'd best
>> share your environment. I've compiled non-trivial C++ programs with clang++
>> and they've behaved properly.
>>
>> -Boris
>>
> One difference I notice between your environment and mine is that, according
> to your bug report, your program links against
> /usr/local/lib/gcc46/libstdc++.so.6, while mine links against
> /usr/lib/libstdc++.so.6.
>
> -Boris
>
I forgot about that. I use gcc46 to build ports and have
libstdc++.so.6 gcc46/libstdc++.so.6
in /etc/libmap.conf

I guess I should close the bug.








--
Eitan Adler
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Anonymous on 29 Jun 2010 23:00
Eitan Adler <lists(a)eitanadler.com> writes:

>> One difference I notice between your environment and mine is that, according
>> to your bug report, your program links against
>> /usr/local/lib/gcc46/libstdc++.so.6, while mine links against
>> /usr/lib/libstdc++.so.6.
>>
>> -Boris
>>
> I forgot about that. I use gcc46 to build ports and have
> libstdc++.so.6 gcc46/libstdc++.so.6
> in /etc/libmap.conf

I have clang++ (devel/llvm-devel) built by g++45 and linked against
gcc45/libstdc++.so.6. It compiles your test case fine. But I'm running
9-current on amd64 so it may not be that useful.

IMO, gcc46 being a development branch is prone to miscompile and have bugs.

>
> I guess I should close the bug.
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 |  Next  |  Last
Pages: 1 2 3
Prev: Fwd: [sudo-workers] sudo 1.7.3rc1 available
Next: [Medical package] - Presentation of FreeDiams: Free prescriber