From owner-freebsd-current@FreeBSD.ORG Tue Jun 28 05:42:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91AE5106566B for ; Tue, 28 Jun 2011 05:42:18 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id 437C58FC16 for ; Tue, 28 Jun 2011 05:42:17 +0000 (UTC) X-AuditID: 1209190f-b7b0eae000000a42-01-4e0969bbc88d Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id F9.D3.02626.BB9690E4; Tue, 28 Jun 2011 01:42:19 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p5S5gGww024380; Tue, 28 Jun 2011 01:42:16 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p5S5gF0f015438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Jun 2011 01:42:16 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id p5S5gEiO009413; Tue, 28 Jun 2011 01:42:14 -0400 (EDT) Date: Tue, 28 Jun 2011 01:42:14 -0400 (EDT) From: Benjamin Kaduk To: Eric McCorkle In-Reply-To: Message-ID: References: <4E07EBA2.70500@shadowsun.net> <4E08778D.2050302@FreeBSD.org> <4E08A8DB.2020805@shadowsun.net> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixG6nrrs7k9PPYOtNIYv/L3YxWcx584HJ gcljxqf5LB5XVn5iDmCK4rJJSc3JLEst0rdL4Mp4P3E5a8E2roqzx7rZGxjncHQxcnJICJhI dG+/zwphi0lcuLeerYuRi0NIYB+jxOGGD8wgCSGBDYwSN75IQNgHmCTuzYuBKGpglFjxaiM7 SIJFQFviyOGVYDabgIrEzDcb2UBsEQE1iV9Nm1hAbGYBeYn/Vy4zgdjCAv4Ss761gsU5BRwl JpybCLaMV8BB4vSP30wQC+YzSuybcgWsQVRAR2L1/iksEEWCEidnPoEaailx7s91tgmMgrOQ pGYhSS1gZFrFKJuSW6Wbm5iZU5yarFucnJiXl1qka6KXm1mil5pSuokRFKqckvw7GL8dVDrE KMDBqMTDy7SSw0+INbGsuDL3EKMkB5OSKO/8DE4/Ib6k/JTKjMTijPii0pzU4kOMEhzMSiK8 U42AcrwpiZVVqUX5MClpDhYlcd5y7/++QgLpiSWp2ampBalFMFkZDg4lCd7FIEMFi1LTUyvS MnNKENJMHJwgw3mAhs8DqeEtLkjMLc5Mh8ifYlSUEuddAJIQAElklObB9cJSyStGcaBXhHkX glTxANMQXPcroMFMQIN1TDlABpckIqSkGhg9p4m0dGs3PTLhEum6E+wbUpGus//g7WDpM0wn HX8WnXpddIPnVQQfm2tVUWbT9a7ezU/3/tpyI6dujce72TPudEvv/aIz97K16oIpBlddz2jb amft99XZL/1i2l3r/5/1J7wRM1SamSbyRTmqbM6sB56mWUon0yLvah7uYTT4VaPI877QU02J pTgj0VCLuag4EQB7ltiFAAMAAA== Cc: freebsd-current@freebsd.org Subject: Re: Clang buildworld failure due to multiple definitions of __isnanf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Jun 2011 05:42:18 -0000 On Tue, 28 Jun 2011, Benjamin Kaduk wrote: > On Mon, 27 Jun 2011, Eric McCorkle wrote: > >> make.conf: >> CPUTYPE?=core2 >> .if !defined(CC) || ${CC} == "cc" >> CC=clang >> CFLAGS=-Qunused-arguments >> .endif >> .if !defined(CXX) || ${CXX} == "c++" >> CXX=clang++ >> .endif >> NO_WERROR= >> WERROR= >> NO_FSCHG= >> PERL_VERSION=5.12.3 >> >> Just noticed, the CFLAGS would disable optimization, which would explain >> why no one else seems to see this. Still, I think the underlying issue >> warrants investigation. > > I seem to recall that our gcc-4.2 with -O0 is known to be buggy -- certainly > I just tripped over a panic in a third-party kernel module build using > bsd.kmod.mk with -O0 that was fixed by compiling the object in question with > -O. > It is not terribly easy to search for, but my archives find at least > http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076028.html > > I would try with -O1 and confirm that your issues go away, and not spend time > on the core issue if it proves to be a gcc bug. > > Unfortunately, we are stuck with an old gcc in base ... though I have yet to > see if clang -O0 has issues with my module. Wow, I juxtaposed the two compilers due to working on too little sleep. Please disregard, and sorry for the noise. -Ben