This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/29609] [4.1/4.2/4.3 Regression] Even with -O0 -g gcc optimizes a goto away and I cannot debug
- From: "hainque at adacore dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Dec 2007 08:30:30 -0000
- Subject: [Bug middle-end/29609] [4.1/4.2/4.3 Regression] Even with -O0 -g gcc optimizes a goto away and I cannot debug
- References: <bug-29609-5724@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from hainque at adacore dot com 2007-12-19 08:30 -------
Subject: Re: [4.1/4.2/4.3 Regression] Even with -O0 -g gcc optimizes a goto
away and I cannot debug
Hi Steven,
steven at gcc dot gnu dot org wrote:
> xf. http://gcc.gnu.org/ml/gcc-patches/2007-04/msg01789.html
>
> I was wrong to object to this patch
No problem, and many thanks for getting back to us on this issue.
What really matters is feedback/discussion IMO, and your comments had
us look for better ways to perform the task. This is a positive outcome
even if we haven't (yet) pushed further for an inclusion into the FSF
tree.
> there really doesn't seem to be any other way. It's funny, on the
> one hand we complain about the code quality of -O0, but on the other
> we have to do quite silly things such as adding jumps to jumps to
> keep rather important debug information around...
Right. We have several constraints at play (want to debug, want the
ability to debug (-g) not to modify the generated code, and want to
limit generated code bloats), and it's not always possible to progress
on one aspect without effects on the others.
I like the recently suggested "-Og" idea because it offers a way through.
> Olivier, any chance someone at AdaCore can pick this up and re-submit it to
> gcc-patches?
We can definitely resubmit the current version we have (I copied the
author). Thanks again for your feedback,
Olivier
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29609