Confirming a bug in clang++ (freeBSD

Eitan Adler lists at eitanadler.com
Thu Jul 1 15:48:26 UTC 2010


On Tue, Jun 29, 2010 at 11:00 PM, Anonymous <swell.k at gmail.com> wrote:
> Eitan Adler <lists at 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'm not that familiar with with mapping. Since g++46/* is built with
g++46 and my program is compiled by clang++ is it expected that they
be compatible?
If yes does that mean this is a bug in g++46 or clang++?

-- 
Eitan Adler


More information about the freebsd-ports mailing list