From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6507 invoked by alias); 22 Jul 2006 20:05:10 -0000 Received: (qmail 6389 invoked by uid 48); 22 Jul 2006 20:05:00 -0000 Date: Sat, 22 Jul 2006 20:05:00 -0000 Message-ID: <20060722200500.6388.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug debug/27574] [4.1 Regression] MIssing debug info at -O0 for a local variable in a C++ constructor In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "drow at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-07/txt/msg01715.txt.bz2 List-Id: ------- 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 regression hunter to identify what patch caused the string "problem" to appear in the assembly output. It is probably something in the last two and a half months, since the bug was reported, but I do not see any obvious candidates. -- drow at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|drow at gcc dot gnu dot org |unassigned at gcc dot gnu | |dot org Status|ASSIGNED |NEW Summary|[4.1/4.2 Regression] MIssing|[4.1 Regression] MIssing |debug info at -O0 for a |debug info at -O0 for a |local variable in a C++ |local variable in a C++ |constructor |constructor http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27574