From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19033 invoked by alias); 25 Jul 2006 12:14:55 -0000 Received: (qmail 18956 invoked by uid 48); 25 Jul 2006 12:14:46 -0000 Date: Tue, 25 Jul 2006 12:14:00 -0000 Message-ID: <20060725121446.18955.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: "amylaar 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/msg01916.txt.bz2 List-Id: ------- 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 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. > 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? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27574