From owner-freebsd-current@FreeBSD.ORG Fri Nov 9 17:00:13 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C56C8D6; Fri, 9 Nov 2012 17:00:13 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 37BCA8FC08; Fri, 9 Nov 2012 17:00:13 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.5/8.14.5) with ESMTP id qA9H0CWX061179; Fri, 9 Nov 2012 09:00:12 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.5/8.14.5/Submit) id qA9H0Cd9061178; Fri, 9 Nov 2012 09:00:12 -0800 (PST) (envelope-from sgk) Date: Fri, 9 Nov 2012 09:00:12 -0800 From: Steve Kargl To: Roman Divacky Subject: Re: clang and static linking? Message-ID: <20121109170012.GA61150@troutmask.apl.washington.edu> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121109164541.GA34499@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Konstantin Belousov , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 17:00:13 -0000 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