public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-55257-4-nPXbSkG7fp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55257-4@http.gcc.gnu.org/bugzilla/>


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).


  parent reply	other threads:[~2012-11-12 17:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10  1:52 [Bug debug/55257] New: " hp at gcc dot gnu.org
2012-11-12  7:51 ` [Bug debug/55257] " jakub at gcc dot gnu.org
2012-11-12 17:08 ` hp at gcc dot gnu.org
2012-11-12 17:15 ` jakub at gcc dot gnu.org [this message]
2012-11-12 17:22 ` hp at gcc dot gnu.org
2012-11-13  6:14 ` [Bug target/55257] " hp at gcc dot gnu.org
2012-11-13  6:16 ` hp at gcc dot gnu.org
2012-11-13  6:39 ` hp at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55257-4-nPXbSkG7fp@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).