From: Keith Seitz <keiths@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [testcase patch] 7.2 regression on expand psymtabs
Date: Tue, 14 Dec 2010 16:18:00 -0000 [thread overview]
Message-ID: <4D0798D4.5040000@redhat.com> (raw)
In-Reply-To: <20101214070638.GP2596@adacore.com>
On 12/13/2010 11:06 PM, Joel Brobecker wrote:
> Sorry to be so behind on gdb-patches email. Has this been resolved?
> Does it affect the 7.2.1 release?
This is c++/11734 (psymtab expansion of overloaded methods), for which I
have an outstanding patch. Tom has asked me to make a few API changes to
support it, but yesterday I got tangled in decode_compound again, and I
didn't get back to 11734. I'll give c++/11734 my top priority today.
I'm sure it affects every release since the original dwarf2_physname
patch was committed in March.
Keith
next prev parent reply other threads:[~2010-12-14 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 21:30 Jan Kratochvil
2010-12-14 7:06 ` Joel Brobecker
2010-12-14 16:18 ` Keith Seitz [this message]
2010-12-14 16:20 ` Tom Tromey
2011-10-21 15:31 ` Jan Kratochvil
2011-10-21 18:48 ` [commit] " Jan Kratochvil
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=4D0798D4.5040000@redhat.com \
--to=keiths@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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