Date: Thu, 1 Jul 2010 14:32:49 -0400 From: Eitan Adler <lists@eitanadler.com> To: Anonymous <swell.k@gmail.com> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: Confirming a bug in clang++ (freeBSD Message-ID: <AANLkTimB5DX9y-TkEubRF3IQxt51jZNHuaKmESRQZFbv@mail.gmail.com> In-Reply-To: <86630z85fg.fsf@gmail.com> References: <AANLkTink7JcqKh4J2Q72CsQ3J-DqYagSB0izFho5GnYX@mail.gmail.com> <4C297844.2030500@acm.poly.edu> <4C29796C.7070901@acm.poly.edu> <AANLkTil-g_TrS_lZs75BfAotTJE4x67tloippJAz8H6V@mail.gmail.com> <86vd91b4xk.fsf@gmail.com> <AANLkTinF8N_TNwdlrmZOVk1JcyeQkj3XMsswphp84VUk@mail.gmail.com> <86630z85fg.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> 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 ? -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimB5DX9y-TkEubRF3IQxt51jZNHuaKmESRQZFbv>