public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "b.r.longbons at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/58150] New: debug info about definition of enum class not emitted if the declaration was already used in a template
Date: Wed, 14 Aug 2013 00:08:00 -0000	[thread overview]
Message-ID: <bug-58150-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58150
           Summary: debug info about definition of enum class not emitted
                    if the declaration was already used in a template
           Product: gcc
           Version: 4.8.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: b.r.longbons at gmail dot com

Created attachment 30649
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30649&action=edit
minimal testcase

If an enum class has a forward declaration and it is used as a class member
(functions seem to be okay), the full debuginfo is not emitted when the
definition appear later in the TU.

This makes debugging practically impossible.

enums are unusual in that they can be fully used even when they have just a
definition.

Tested gcc versions:
g++-4.6 (Debian 4.6.4-2) 4.6.4
g++-4.7 (Debian 4.7.3-4) 4.7.3
g++-4.8 (Debian 4.8.1-8) 4.8.1

Versions before 4.6 did not implement forward declarations of enum classes, so
this bug is primordial.

The relevant part of the debug information looks like:

 <1><34>: Abbrev Number: 3 (DW_TAG_enumeration_type)
    <35>   DW_AT_name        : (indirect string, offset: 0x84): ByteCode
    <39>   DW_AT_enum_class  : 1
    <39>   DW_AT_declaration : 1
    <39>   DW_AT_byte_size   : 1
    <3a>   DW_AT_decl_file   : 1
    <3b>   DW_AT_decl_line   : 3

Whereas clang generates:

 <1><6f>: Abbrev Number: 6 (DW_TAG_enumeration_type)
    <70>   DW_AT_type        : <0x64>
    <74>   DW_AT_enum_class  : 1
    <75>   DW_AT_name        : (indirect string, offset: 0x98): ByteCode
    <79>   DW_AT_byte_size   : 1
    <7a>   DW_AT_decl_file   : 1
    <7b>   DW_AT_decl_line   : 10


                 reply	other threads:[~2013-08-14  0:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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