Date: Mon, 4 Sep 2000 14:37:36 +0100 From: Steve Roome <steve@sse0691.bri.hp.com> To: "Chad R. Larson" <chad@DCFinc.com> Cc: stable@freebsd.org Subject: Re: GCC bug with 4.1-stable Message-ID: <20000904143736.A12903@moose.bri.hp.com> In-Reply-To: <200008312111.OAA29206@freeway.dcfinc.com>; from chad@DCFinc.com on Thu, Aug 31, 2000 at 02:11:18PM -0700 References: <20000831133004.B90719@moose.bri.hp.com> <200008312111.OAA29206@freeway.dcfinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 31, 2000 at 02:11:18PM -0700, Chad R. Larson wrote: > As I recall, Steve Roome wrote: > > Yes, the actual problem seems to be "-mno-move -mcpu=pentiumpro", even > > with -O0 this will crash. [which gcc explaining it has crashed, not > > just some random sig11 that some git is going to argue is RAM > > related!] > > Have you launched this at the GCC folks? Yup. IIRC, it's optimization/496 (can't check at the moment though) > > The other problem is slightly odd : > > > > gcc -mno-ieee-fp -march=pentiumpro -c particlesys.c -o particlesys.o > > gcc: Internal compiler error: program cc1 got fatal signal 11 > > *** Error code 1 > > Signal 11 is a segmentation violation. Usually dereferencing an > uninitialized, null or trashed pointer. Yup, it's only seeming to happen with -mno-ieee-fp and pentiumpro options. So I guess there really is something screwy there. I'll file a pr for this. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000904143736.A12903>