Date: Thu, 26 Apr 2001 08:19:54 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Jason Andresen <jandrese@mitre.org> Cc: Dag-Erling Smorgrav <des@ofug.org>, hackers@freebsd.org Subject: Re: gcc -O bug Message-ID: <20010426081954.A72609@dragon.nuxi.com> In-Reply-To: <3AE82644.50ED4A0@mitre.org>; from jandrese@mitre.org on Thu, Apr 26, 2001 at 09:44:36AM -0400 References: <xzplmonx31m.fsf@flood.ping.uio.no> <3AE82644.50ED4A0@mitre.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 26, 2001 at 09:44:36AM -0400, Jason Andresen wrote:
> Er, isn't this the kind of problem the GCC folks are more likly to be
> able to fix?
In general yes. But it doesn't hurt to double check here to make sure
you your ducks in row before going to the GCC lists. I see later in this
thread DES found it was a coding problem, not GCC optimizer problem.
> At least in GCC 2.9.5 (not the latest mind you) this problem still
^^^^^
2.95[.3]
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010426081954.A72609>