From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31504 invoked by alias); 28 Aug 2004 00:20:12 -0000 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 Received: (qmail 31483 invoked by alias); 28 Aug 2004 00:20:11 -0000 Date: Sat, 28 Aug 2004 00:20:00 -0000 Message-ID: <20040828002011.31482.qmail@sourceware.org> From: "mec dot gnu at mindspring dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040206163854.14049.mec.gnu@mindspring.com> References: <20040206163854.14049.mec.gnu@mindspring.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug middle-end/14049] [3.5 regression] bad debug block info, dwarf-2, c++ X-Bugzilla-Reason: CC X-SW-Source: 2004-08/txt/msg02923.txt.bz2 List-Id: ------- Additional Comments From mec dot gnu at mindspring dot com 2004-08-28 00:20 ------- Subject: Re: [3.5 regression] bad debug block info, dwarf-2, c++ I checked again with gcc HEAD 20040824 and the bug in scope.c has been fixed. The bug in block.cc is also still fixed. The gdb test suite is happy too. This was manifesting as regressions in gdb.mi/mi-var-block.exp and gdb.mi/mi2-var-block.exp. I couldn't see the fixed results in my test bed because the gdb.mi/*.exp tests got blinded by the new warning for "incompatible implicit declaration of built-in function". The tests themselves just got fixed a few days ago. So I think this PR can go to RESOLVED/FIXED now. I don't think it would be worth my time to chase down the patch that caused the bug or the patch that fixed it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14049