From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [patch-testcase] Re: [rfc] Work around buggy GCC 4.1 namespace dwarf info (GCC PR c++/28460)
Date: Sat, 20 Mar 2010 01:30:00 -0000 [thread overview]
Message-ID: <m3y6hnwzi8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100319192008.GA1980@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri, 19 Mar 2010 20:20:08 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> this problem was fixed before at:
Jan> [expr-cumulative] Fix namespace regression for G++-4.1
Jan> http://sourceware.org/ml/archer/2009-q4/msg00124.html
If you have other patches on expr-cumulative, it would be good to submit
them.
I think all my patches from that branch are in, and I know Sami is
working on his.
Tom
next prev parent reply other threads:[~2010-03-20 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 12:37 Ulrich Weigand
2010-03-19 12:59 ` Daniel Jacobowitz
2010-03-19 19:20 ` [patch-testcase] " Jan Kratochvil
2010-03-19 20:21 ` Daniel Jacobowitz
2010-03-20 1:30 ` Tom Tromey [this message]
2010-03-21 19:42 ` Jan Kratochvil
2010-03-22 13:23 ` Ulrich Weigand
2010-03-22 16:55 ` 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=m3y6hnwzi8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=uweigand@de.ibm.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