Confirming a bug in clang++ (freeBSD
lists at eitanadler.com
Thu Jul 1 18:33:10 UTC 2010
>>> 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
> It's more interesting which gcc version you used for compiling clang.
I forgot. Most likely it was base gcc as I have an exemption in my
/etc/make.conf for it.
>> 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++?
> Either -lstdc++ from gcc46 is buggy or just clang++ doesn't like it.
> It's better to use -lstdc++ from same version of gcc by which the
> program using it was compiled.
Is it possible to determine which one?
Is this something that is my fault for playing around too much or did
I expose a bug ?
More information about the freebsd-ports