From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [1/4] RFC: skip DIEs which only declare an enum
Date: Mon, 18 Jul 2011 18:02:00 -0000 [thread overview]
Message-ID: <m3oc0r7cs1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAN9gPaGvXL=300R7HeGPhyAk7EzpZg=xFg7GpOfrO07eMQQHWA@mail.gmail.com> (Daniel Jacobowitz's message of "Fri, 15 Jul 2011 14:27:46 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> Generally speaking, I agree with your sentiment. Can't you
Daniel> forward-declare enums in the latest C++ draft, though?
Yes, thanks for pointing that out. The F15 g++ accepts this translation
unit with -std=c++0x:
enum x : int;
enum x a;
This generates:
<1><1d>: Abbrev Number: 2 (DW_TAG_enumeration_type)
<1e> DW_AT_name : x
<20> DW_AT_declaration : 1
<21> DW_AT_byte_size : 4
<22> DW_AT_decl_file : 1
<23> DW_AT_decl_line : 1
I am going withdraw this patch and look at other ways to fix this
problem.
Tom
next prev parent reply other threads:[~2011-07-18 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 18:08 Tom Tromey
2011-07-15 18:50 ` Daniel Jacobowitz
2011-07-18 18:02 ` Tom Tromey [this message]
2011-07-18 20:14 ` Tom Tromey
2011-07-20 15:19 ` Tom Tromey
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=m3oc0r7cs1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.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