Date: Mon, 23 Jul 2001 13:00:02 -0700 (PDT) From: Mike Barcroft <mike@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/19245: -fexpensive-optimizations buggy (even with -O) Message-ID: <200107232000.f6NK02r31180@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: Mike Barcroft <mike@FreeBSD.org> To: Mikhail Teterin <mi@aldan.algebra.com> Cc: bde@FreeBSD.org, freebsd-gnats-submit@FreeBSD.org Subject: Re: i386/19245: -fexpensive-optimizations buggy (even with -O) Date: Mon, 23 Jul 2001 16:07:29 -0400 On Mon, Jul 23, 2001 at 12:21:58PM -0400, Mikhail Teterin wrote: > On 21 Jul, mike@FreeBSD.org wrote: > > Synopsis: -fexpensive-optimizations buggy (even with -O) > > > > State-Changed-From-To: open->closed > > State-Changed-By: mike > > State-Changed-When: Sat Jul 21 20:12:42 PDT 2001 > > State-Changed-Why: > > > > 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 discussed numerous times on the mailing lists. Also, we directly import vendor code, so this problem must be fixed by the GCC people. A quick search of the GCC Gnats database reveals many bug reports involving optimisation problems. If your problem isn't addressed in one of those PR's, may I recommend you open a new one there? 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 PR to be left open. It may seem as though I'm on a "PR-closing trip" to you, but I assure you my intentions are to determine if problems from years ago are still problems today. There are many PR's in our datebase that should have been closed a long time ago. I feel this PR is one of them. Best regards, Mike Barcroft 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?200107232000.f6NK02r31180>