public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.smets@alcatel-lucent.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/56805] DW_TAG_typedef missing when -fdebug-types-section is used (and -fno-eliminate-unused-debug-types)
Date: Fri, 12 Apr 2013 09:38:00 -0000	[thread overview]
Message-ID: <bug-56805-4-6ynP4vuoxf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56805-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #6 from Jan Smets <jan.smets@alcatel-lucent.com> 2013-04-12 09:38:52 UTC ---
What if we created a new .debug_types section for the typedef if:
 1)  -fno-eliminate-unused-debug-types is used
 2)  a typedef is unused and otherwise eliminated.

By doing this we won't create excessive information for people who are using
debug-types-sections and who want a compact set of debugging info. Would that
be possible?

Thanks


  parent reply	other threads:[~2013-04-12  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 23:25 [Bug debug/56805] New: DW_AT_typedef " jan.smets@alcatel-lucent.com
2013-04-01 23:33 ` [Bug debug/56805] " jan.smets@alcatel-lucent.com
2013-04-02 17:40 ` [Bug debug/56805] DW_TAG_typedef " ccoutant at gcc dot gnu.org
2013-04-02 18:11 ` jan.smets@alcatel-lucent.com
2013-04-02 20:35 ` ccoutant at gcc dot gnu.org
2013-04-02 20:36 ` ccoutant at gcc dot gnu.org
2013-04-02 21:28 ` jan.smets@alcatel-lucent.com
2013-04-12  9:38 ` jan.smets@alcatel-lucent.com [this message]
2013-09-03  9:01 ` jan.smets@alcatel-lucent.com

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-56805-4-6ynP4vuoxf@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).