--- Comment #11 from amylaar at gcc dot gnu dot org 2006-07-26 12:30
---
(In reply to comment #10)
If I had to guess I'd say that this was a C++ front end problem, or
maybe a recent change in cgraph.
It can't have been a particularly recent change, since it already failed
with GNU
--- Comment #12 from drow at gcc dot gnu dot org 2006-07-26 13:59 ---
It is a cgraph change. There were several patches affecting cgraph_remove_node
during this time period; it was probably one of those. The problem is that we
throw away the body of the abstract copy of the
--- Comment #6 from amylaar at gcc dot gnu dot org 2006-07-25 12:14 ---
(In reply to comment #5)
I am not going to track down what did it, but something has fixed this on the
4.2 branch. I can reproduce it on Debian's 4.1 branch snapshot. If someone
wants to fix it on 4.1, it
--- Comment #7 from drow at gcc dot gnu dot org 2006-07-25 13:27 ---
Subject: Re: [4.1 Regression] MIssing debug info at -O0 for a local variable
in a C++ constructor
On Tue, Jul 25, 2006 at 12:14:46PM -, amylaar at gcc dot gnu dot org wrote:
If this is fixed on mainline, the fix
--- Comment #8 from joern dot rennecke at st dot com 2006-07-25 17:08
---
Subject: Re: [4.1 Regression] MIssing debug info at -O0 for a local variable
in a C++ constructor
drow at false dot org wrote:
--- Comment #7 from drow at gcc dot gnu dot org 2006-07-25 13:27 ---
--- Comment #9 from amylaar at gcc dot gnu dot org 2006-07-25 20:43 ---
Created an attachment (id=11938)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11938action=view)
g++.dg/debug test case
As far as I can tell, as a g++.dg/debug test case, this passes for stabs, but
fails for
--- Comment #10 from drow at gcc dot gnu dot org 2006-07-26 03:52 ---
Subject: Re: [4.1 Regression] MIssing debug info at -O0 for a local variable
in a C++ constructor
On Tue, Jul 25, 2006 at 05:08:18PM -, joern dot rennecke at st dot com
wrote:
When I compile the testcase (using
--- Comment #5 from drow at gcc dot gnu dot org 2006-07-22 20:05 ---
I am not going to track down what did it, but something has fixed this on the
4.2 branch. I can reproduce it on Debian's 4.1 branch snapshot. If someone
wants to fix it on 4.1, it should probably be easy to use the
