From owner-freebsd-questions@FreeBSD.ORG Thu Jul 17 22:59:14 2014 Return-Path: Delivered-To: freebsd-questions@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 01464980 for ; Thu, 17 Jul 2014 22:59:14 +0000 (UTC) Received: from relay.exonetric.net (relay0.exonetric.net [178.250.72.161]) by mx1.freebsd.org (Postfix) with ESMTP id C3E1E2A8B for ; Thu, 17 Jul 2014 22:59:13 +0000 (UTC) Received: from [192.168.10.18] (186.211.187.81.in-addr.arpa [81.187.211.186]) by relay.exonetric.net (Postfix) with ESMTPSA id ACC962CDB6; Thu, 17 Jul 2014 23:51:33 +0100 (BST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Bug report From: Mark Blackman In-Reply-To: <867g3bvd33.fsf@shell.gmplib.org> Date: Thu, 17 Jul 2014 23:51:32 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <27C0CC10-FCBB-4412-890E-C94DACF60E58@exonetric.com> References: <867g3bvd33.fsf@shell.gmplib.org> To: =?windows-1252?Q?Torbj=F6rn_Granlund?= X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2014 22:59:14 -0000 On 17 Jul 2014, at 23:24, Torbj=F6rn Granlund wrote: >=20 > Result: > bug-fbsdgcc.c: In function 'foo': > bug-fbsdgcc.c:22: internal compiler error: in memory_address_length, = at config/i386/i386.c:13897 > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. >=20 > (I do not report this to the gcc folks in spite of being urged since > this gcc apparently was hacked by fbsd.) Thanks for the very specific and detailed bug report. I=92m sure the = FreeBSD teams would like to know (although even this list is probably = not quite right either) about such a curious bug, I don=92t think there = would be any harm in reporting this to the gcc team. They can choose to = disregard it if they like, but you=92re taking that decision out of = their hands if you don=92t report it. - Mark=