From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9423 invoked by alias); 12 Nov 2012 17:08:35 -0000 Received: (qmail 9208 invoked by uid 48); 12 Nov 2012 17:08:12 -0000 From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/55257] [4.8 Regression]: g++.dg/debug/dwarf2/non-virtual-thunk.C scan-assembler thunk.C:30 Date: Mon, 12 Nov 2012 17:08:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Keywords: wrong-debug X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: hp at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.0 X-Bugzilla-Changed-Fields: Status Last reconfirmed AssignedTo Target Milestone Ever Confirmed Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg01038.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55257 Hans-Peter Nilsson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2012-11-12 AssignedTo|unassigned at gcc dot |hp at gcc dot gnu.org |gnu.org | Target Milestone|--- |4.8.0 Ever Confirmed|0 |1 --- Comment #2 from Hans-Peter Nilsson 2012-11-12 17:08:12 UTC --- (In reply to comment #1) > If the target doesn't call final_start_function and final_end_function in > output_mi_thunk targhook (or equivalent), it is a target bug. I see. I either missed this requirement when I implemented those bits for CRIS or it wasn't a requirement at the time. BTW, I see several ports are missing those calls. I guess in the general case it can't be left to middle-end to call those functions at the right time, so I'll just update the port and hopefully the documentation, but no promises. Assigning the PR to myself while verifying that this is the cause.