Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Aug 2001 05:30:01 -0700 (PDT)
From:      Bruce Evans <bde@zeta.org.au>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: i386/19245: -fexpensive-optimizations buggy (even with -O)
Message-ID:  <200108291230.f7TCU1K01950@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/19245; it has been noted by GNATS.

From: Bruce Evans <bde@zeta.org.au>
To: Mike Barcroft <mike@FreeBSD.org>
Cc: Mikhail Teterin <mi@aldan.algebra.com>, <bde@FreeBSD.org>,
	<freebsd-gnats-submit@FreeBSD.org>
Subject: Re: i386/19245: -fexpensive-optimizations buggy (even with -O)
Date: Wed, 29 Aug 2001 22:27:24 +1000 (EST)

 On Mon, 23 Jul 2001, Mike Barcroft wrote:
 
 > On Mon, Jul 23, 2001 at 12:21:58PM -0400, Mikhail Teterin wrote:
 > > On 21 Jul, mike@FreeBSD.org wrote:
 > > > GCC has major problems with optimisation.  See bde's comments for
 > > > details.
 > >
 > > First, BDE did not close the PR himself, despite his comments. Second,
 > > the same "troublesome" GCC produces correct code on Linux, which was
 > > one of the major points of my PR -- something was/is wrong with the
 > > FreeBSD-specific part of gcc-2.95.2... But, it seems, you are on a
 > > PR-closing trip...
 >
 > Sorry if this was made unclear.  GCC is known to do bad things when
 > using anything but -O for optimisation on FreeBSD.  This has been
 > ...
 > There could be any number of reasons why Bruce didn't close your
 > PR then and there.  Bruce is a very busy person and might not have
 > had time to close this PR.  I'm CC'ing Bruce on this message to
 > see if I missed something in his comments that would require this
 
 The main reason reason is that I wasn't sure that it was not a FreeBSD
 bug.  There is now a near-duplicate of this PR (gnu/30181) which says
 that the bug is in both the FreeBSD port and original GNU version of
 gcc-2.95.3, and analyses generated code to locate the wrong instructions.
 It's clear that it is a gcc bug.
 
 I don't plan to fix this.  PR 30181 suggests mentioning the problem in
 the release notes.  This seems reasonable.  I think the PRs should be
 cross-refernced, and closed after doing this.
 
 Bruce
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108291230.f7TCU1K01950>