This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/27574] [4.1 Regression] MIssing debug info at -O0 for a local variable in a C++ constructor
- From: "joern dot rennecke at st dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Jul 2006 17:08:18 -0000
- Subject: [Bug debug/27574] [4.1 Regression] MIssing debug info at -O0 for a local variable in a C++ constructor
- References: <bug-27574-5394@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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 -------
>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 -0000, amylaar at gcc dot gnu dot org wrote:
>
>
>>If this is fixed on mainline, the fix must be rather recent; I see this still
>>failing with
>>r115417: GNU C++ version 4.2.0 20060713 (experimental).
>>What is the oldest gcc 4.2 version where you saw this work?
>>
>>
>
>I tested it on HEAD on the day I posted (2006-07-22). Could you check
>whether that works for you, or it's something environmental?
>
>
When I compile the testcase (using -g -O0) with a cc1plus built from todays
sources (r115734), a test search for "problem" in the .s file comes up
empty.
OTOH, both a native and a cross build eventually failed.
Can you find out the exact version of gcc that you tested?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27574