From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-406377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 13737 invoked by alias); 12 Nov 2012 17:15:06 -0000
Received: (qmail 13324 invoked by uid 48); 12 Nov 2012 17:14:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.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:15: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: jakub 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:
Message-ID: <bug-55257-4-nPXbSkG7fp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55257-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-11/txt/msg01039.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55257

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-12 17:14:41 UTC ---
It is a requirement if you want proper debug info or unwind info for the thunk,
without that (or without calling the corresponding functions yourself, which is
harder to maintain) you don't get proper debug info.  It can't be called from
the middle end, because some targets need to perform various things before
final_start_function (or perhaps after final_end_function).