From owner-freebsd-current@FreeBSD.ORG Thu Feb 27 00:57:54 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7A19C45 for ; Thu, 27 Feb 2014 00:57:54 +0000 (UTC) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A97471103 for ; Thu, 27 Feb 2014 00:57:54 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id s1R0vkjH084327; Wed, 26 Feb 2014 16:57:51 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201402270057.s1R0vkjH084327@gw.catspoiler.org> Date: Wed, 26 Feb 2014 16:57:46 -0800 (PST) From: Don Lewis Subject: Re: firebox build fails post clang-3.4 merge To: imb@protected-networks.net In-Reply-To: <530E35F4.1090909@protected-networks.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: 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 00:57:54 -0000 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 . I tried compiling the offending file with gcc46 and didn't see the problem in the assembly output.