public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/27574] [4.1 Regression] MIssing debug info at -O0 for a local variable in a C++ constructor Date: Wed, 26 Jul 2006 13:59:00 -0000 [thread overview] Message-ID: <20060726135933.30452.qmail@sourceware.org> (raw) In-Reply-To: <bug-27574-5394@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from drow at gcc dot gnu dot org 2006-07-26 13:59 ------- It is a cgraph change. There were several patches affecting cgraph_remove_node during this time period; it was probably one of those. The problem is that we throw away the body of the abstract copy of the constructor, before we get around to emitting debug information for it. There's already a debug hook at what looks like the right time. It's just not used for dwarf2: deferred_inline_function. It was replaced by outlining_inline_function, which is called only when we know we'll generate a concrete instance. There's a couple of things we could do: - Not throw away the body. - Try to generate the debug info earlier, and then prune it if it isn't needed. - Try to treat one of the concrete clones (whose bodies we need) as the origin. I think the first one is going to be safest for now. I don't really see how to do it. Jan, do you have a suggestion? -- drow at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27574
next prev parent reply other threads:[~2006-07-26 13:59 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-12 16:53 [Bug debug/27574] New: MIssing debug info at -O0 amylaar at gcc dot gnu dot org 2006-05-12 16:58 ` [Bug debug/27574] " amylaar at gcc dot gnu dot org 2006-05-12 17:02 ` amylaar at gcc dot gnu dot org 2006-05-12 17:11 ` [Bug debug/27574] [4.1/4.2 Regression] MIssing debug info at -O0 for a C++ constructor pinskia at gcc dot gnu dot org 2006-05-14 22:39 ` [Bug debug/27574] [4.1/4.2 Regression] MIssing debug info at -O0 for a local variable in " mmitchel at gcc dot gnu dot org 2006-05-25 2:41 ` mmitchel at gcc dot gnu dot org 2006-07-22 17:46 ` drow at gcc dot gnu dot org 2006-07-22 20:05 ` [Bug debug/27574] [4.1 " drow at gcc dot gnu dot org 2006-07-25 12:14 ` amylaar at gcc dot gnu dot org 2006-07-25 13:28 ` drow at false dot org 2006-07-25 17:09 ` joern dot rennecke at st dot com 2006-07-25 20:43 ` amylaar at gcc dot gnu dot org 2006-07-26 3:52 ` drow at false dot org 2006-07-26 12:30 ` amylaar at gcc dot gnu dot org 2006-07-26 13:59 ` drow at gcc dot gnu dot org [this message] 2006-07-27 17:29 ` [Bug debug/27574] [4.1/4.2 " amylaar at gcc dot gnu dot org 2006-07-27 20:12 ` drow at false dot org 2006-08-25 18:57 ` drow at gcc dot gnu dot org 2007-02-14 9:12 ` [Bug debug/27574] [4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2008-01-13 13:51 ` pinskia at gcc dot gnu dot org 2008-01-13 14:46 ` rguenth at gcc dot gnu dot org 2008-02-15 21:28 ` pinskia at gcc dot gnu dot org 2008-02-15 21:30 ` pinskia at gcc dot gnu dot org 2008-04-01 7:12 ` [Bug debug/27574] [4.1/4.2/4.3/4.4 " pinskia at gcc dot gnu dot org 2008-04-23 22:34 ` ian at airs dot com 2008-04-23 23:09 ` pinskia at gcc dot gnu dot org 2008-07-04 21:23 ` [Bug debug/27574] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-10-07 20:52 ` dodji at gcc dot gnu dot org 2008-11-06 10:26 ` dodji at gcc dot gnu dot org 2008-11-12 22:00 ` dodji at gcc dot gnu dot org 2008-11-13 10:57 ` [Bug debug/27574] [4.2/4.3 " dodji at gcc dot gnu dot org 2008-11-14 13:29 ` dodji at gcc dot gnu dot org 2008-11-19 0:18 ` dodji at gcc dot gnu dot org 2008-11-19 0:22 ` dodji at gcc dot gnu dot org 2008-12-09 18:27 ` amylaar at gcc dot gnu dot org 2008-12-09 18:50 ` amylaar at gcc dot gnu dot org 2009-04-29 15:08 ` pinskia at gcc dot gnu dot org 2009-04-29 15:09 ` pinskia at gcc dot gnu dot 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=20060726135933.30452.qmail@sourceware.org \ --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: linkBe 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).