From owner-freebsd-toolchain@freebsd.org Mon Jul 10 02:07:06 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABD59D9ADE8; Mon, 10 Jul 2017 02:07:06 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (ainaz.pair.com [209.68.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89C4F778E0; Mon, 10 Jul 2017 02:07:06 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from ainaz.pair.com (localhost [127.0.0.1]) by ainaz.pair.com (Postfix) with ESMTP id 5CD2B3F5FB; Sun, 9 Jul 2017 22:06:58 -0400 (EDT) Received: from [10.71.4.0] (unknown [103.244.102.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 894623F5FA; Sun, 9 Jul 2017 22:06:56 -0400 (EDT) Date: Mon, 10 Jul 2017 10:06:51 +0800 (+08) From: Gerald Pfeifer To: Mark Millard cc: freebsd-ppc@freebsd.org, freebsd-toolchain@freebsd.org Subject: Re: [toolchain] system clang on powerpc64 vs building lang/gcc7-devel with it: xgcc gets segmentation fault In-Reply-To: <493B86B0-608C-4DCF-83F4-398385F8F01D@dsl-only.net> Message-ID: References: <493B86B0-608C-4DCF-83F4-398385F8F01D@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 02:07:06 -0000 On Tue, 4 Jul 2017, Mark Millard wrote: > I have submitted: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81315 > for the below, presuming for now that the problem is on the GCC side > of things. Hopefully it is not tied to include-fixed/ now being empty. > > [We will see if the GCC folks object to the include-fixed/ having > empty or not.] Internal Compiler Errors (ICEs) are among my favorite bugs since there can hardly be any debate about whether there is a bug there or not - the compiler is never supposed to crash. ;-) Gerald