From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: update for GCC PR 47510
Date: Tue, 29 Mar 2011 17:19:00 -0000 [thread overview]
Message-ID: <m3vcz1oojy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3mxksxzii.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 18 Mar 2011 08:40:53 -0600")
>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
Tom> There was an earlier thread about this bug:
Tom> http://sourceware.org/ml/gdb-patches/2011-02/msg00029.html
Tom> Since then, a different patch has gone into GCC. This new patch puts a
Tom> linkage name onto the otherwise anonymous struct. This is a minor DWARF
Tom> extension that we asked for because the other approaches were a pain to
Tom> implement in GDB. With this new attribute, the patch becomes fairly
Tom> straightforward.
I am checking this in now.
Tom
next prev parent reply other threads:[~2011-03-29 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 14:59 Tom Tromey
2011-03-29 17:19 ` Tom Tromey [this message]
2011-03-30 10:45 ` Regression: " Jan Kratochvil
2011-03-31 19:12 ` Jan Kratochvil
2011-03-31 19:58 ` Jan Kratochvil
2011-03-31 21:03 ` 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=m3vcz1oojy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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