Date: Fri, 9 Nov 2012 09:00:12 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Roman Divacky <rdivacky@freebsd.org> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org Subject: Re: clang and static linking? Message-ID: <20121109170012.GA61150@troutmask.apl.washington.edu> In-Reply-To: <20121109164541.GA34499@freebsd.org> References: <20121108231349.GA79485@troutmask.apl.washington.edu> <20121108234932.GA56820@troutmask.apl.washington.edu> <20121109120012.GB73505@kib.kiev.ua> <20121109164304.GA61011@troutmask.apl.washington.edu> <20121109164541.GA34499@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 09, 2012 at 05:45:41PM +0100, Roman Divacky wrote: > On Fri, Nov 09, 2012 at 08:43:04AM -0800, Steve Kargl wrote: > > On Fri, Nov 09, 2012 at 02:00:12PM +0200, Konstantin Belousov wrote: > > > > > > There is some magic switch to reduce amount of clang bugs, like > > > -fno-integrated-as. Please try to compile the problematic .o with the > > > switch. > > > > I'll try this shortly. Does this mean that we need to build > > all *.a libraries where a weak reference may occur with this > > switch? > > No, this has nothing to do with llvm integrated asm. > > So far it looks like gcc always inline "isnan" even at O0 while > clang does not. We are trying to figure out the solution. > > Maybe use __builtin_isnan instead of isnan in the isnan macro expansion? > Do you want me to file a PR for this? I can continue to use the work around until a proper fix is found. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121109170012.GA61150>