public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pavel.zaytsev at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/55447] New: insufficient debug info for strong typed enum Date: Fri, 23 Nov 2012 13:00:00 -0000 [thread overview] Message-ID: <bug-55447-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55447 Bug #: 55447 Summary: insufficient debug info for strong typed enum Classification: Unclassified Product: gcc Version: 4.5.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: pavel.zaytsev@oracle.com For strong typed enum, there is no type and class information. # cat t.cc enum class Color : long { red = 200, green = 300 }; int main() { Color c; return 0; } #g++ -g -std=c++0x t.cc < 1><0x00000025> DW_TAG_enumeration_type DW_AT_name "Color" DW_AT_byte_size 0x00000004 DW_AT_decl_file 0x00000001 DW_AT_decl_line 0x00000001 DW_AT_sibling <0x00000040> Should have a DW_AT_enum_class and DW_AT_type under DW_TAG_enumeration_type.
next reply other threads:[~2012-11-23 13:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-23 13:00 pavel.zaytsev at oracle dot com [this message] 2012-11-23 14:50 ` [Bug debug/55447] " paolo.carlini at oracle dot 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-55447-4@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: 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).