From owner-freebsd-stable  Mon Sep  4  6:35: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68])
	by hub.freebsd.org (Postfix) with ESMTP id E83EF37B42C
	for <stable@freebsd.org>; Mon,  4 Sep 2000 06:34:42 -0700 (PDT)
Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65])
	by bbnrel4.net.external.hp.com (Postfix) with ESMTP
	id 2CC8E15CEB; Mon,  4 Sep 2000 15:34:40 +0200 (METDST)
Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53])
	by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id OAA27340;
	Mon, 4 Sep 2000 14:34:38 +0100 (BST)
Received: (from steve@localhost)
	by sse0691.bri.hp.com (8.9.3/8.9.3) id OAA12946;
	Mon, 4 Sep 2000 14:37:36 +0100 (BST)
	(envelope-from steve)
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>
References: <20000831133004.B90719@moose.bri.hp.com> <200008312111.OAA29206@freeway.dcfinc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.4i
In-Reply-To: <200008312111.OAA29206@freeway.dcfinc.com>; from chad@DCFinc.com on Thu, Aug 31, 2000 at 02:11:18PM -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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