From owner-freebsd-current@FreeBSD.ORG Thu Feb 27 02:31:59 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B2D9E90; Thu, 27 Feb 2014 02:31:59 +0000 (UTC) Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2557F18CB; Thu, 27 Feb 2014 02:31:58 +0000 (UTC) X-AuditID: 12074424-f79e26d000000c70-aa-530ea26a338a Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id 5D.EA.03184.A62AE035; Wed, 26 Feb 2014 21:26:50 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id s1R2QnNH005666; Wed, 26 Feb 2014 21:26:50 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id s1R2QlB9032413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Feb 2014 21:26:49 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id s1R2QlAZ025535; Wed, 26 Feb 2014 21:26:47 -0500 (EST) Date: Wed, 26 Feb 2014 21:26:47 -0500 (EST) From: Benjamin Kaduk To: Don Lewis Subject: Re: firebox build fails post clang-3.4 merge In-Reply-To: <201402270057.s1R0vkjH084327@gw.catspoiler.org> Message-ID: References: <201402270057.s1R0vkjH084327@gw.catspoiler.org> 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+NgFvrIIsWRmVeSWpSXmKPExsUixCmqrZu1iC/YYPYlG4s5bz4wWSyYMpfd 4mRTM6sDs8eMT/NZPBZN+cgYwBTFZZOSmpNZllqkb5fAlTHrWBd7wTaOikP7H7I1MD5g62Lk 5JAQMJHouHkHyhaTuHBvPZDNxSEkMJtJ4uv890wQzkZGieVfrzFCOIeYJF6sPAyVaWCUeH/o DVg/i4C2xKIb89lBbDYBFYmZbzYCxTk4RIDsbTO4QcLMAtYShz7NZQSxhQVMJdZcbWUCsTkF bCT2TZzNCmLzCjhIHDy8nBWkVQio/veicpCwqICOxOr9U1ggSgQlTs58wgIx0lLi3J/rbBMY BWchSc1CklrAyLSKUTYlt0o3NzEzpzg1Wbc4OTEvL7VI11wvN7NELzWldBMjKGTZXVR2MDYf UjrEKMDBqMTDe4KZL1iINbGsuDL3EKMkB5OSKK/FAqAQX1J+SmVGYnFGfFFpTmrxIUYJDmYl Ed5DLkA53pTEyqrUonyYlDQHi5I4b63FryAhgfTEktTs1NSC1CKYrAwHh5IE7wmQoYJFqemp FWmZOSUIaSYOTpDhPEDDVRaCDC8uSMwtzkyHyJ9iVJQS510H0iwAksgozYPrhaWUV4ziQK8I 86qCtPMA0xFc9yugwUxAg49K84AMLklESEk1MLpayOcl+cgqb7982UwoQqDxTMmyx7e2tk7s vHfcZ+eJpVJnm++blQXeeuZtkta9i73Uz3lDsPbW/Xt1e20W13uyNOicftw/7XLwZuanBQdf frx68U//gdIdEfPv89mrrPj7WDj02MqOVW5z/P2LuWbtXcyuV3L/6KTK7T5186e6aURUebzf eEyJpTgj0VCLuag4EQDlTPjjBAMAAA== Cc: imb@protected-networks.net, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 27 Feb 2014 02:31:59 -0000 On Wed, 26 Feb 2014, Don Lewis wrote: > On 26 Feb, Michael Butler wrote: >> On 02/18/14 12:10, Michael Butler wrote: >>> Is anyone else seeing firefox failing to install after the clang-3.4 >>> merge? As in xpcshell dumping core .. >> >> An update .. >> >> Recompiling with GCC48 on -current yields the same result. Seems to run >> correctly when invoked from the command-line but seg-faults with "errno >> = 4" (invalid instruction) from the build >> >> Giving up and using the Linux port .. :-( > > I've also seen this problem with clang-3.4 on i386. It looks like a > clang bug to me. Clang is putting ud2 instructions in its output which > are guaranteed to fault when it compiles nsAppRunner.cpp. See > . That would seem to indicate that clang believes the source code in question is exercising a case which is explicitly listed as giving undefined behavior in the language specification. Presumably that means we need a C++ language lawyer to look over the code in question. -Ben Kaduk