From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [c++] Pointer to member overhaul
Date: Mon, 08 Jan 2007 15:47:00 -0000 [thread overview]
Message-ID: <200701081547.l08Fler8026574@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070103181514.GC17935@nevyn.them.org> from "Daniel Jacobowitz" at Jan 03, 2007 01:15:14 PM
Dan Jacobowitz wrote:
> I've committed it with Jim's corrections, as below.
>
> A nice bonus: the change to gnuv3_get_virtual_fn fixes two Java tests
> that weren't running before my December testsuite patch.
This also fixes three C++ testcases on s390x-ibm-linux
that have been failing forever there!
Many thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-01-08 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 2:55 Daniel Jacobowitz
2006-12-29 19:06 ` Jim Blandy
2006-12-31 22:40 ` Daniel Jacobowitz
2006-12-31 22:55 ` Eli Zaretskii
2006-12-31 23:49 ` Daniel Jacobowitz
2007-01-03 18:15 ` Daniel Jacobowitz
2007-01-08 15:47 ` Ulrich Weigand [this message]
2007-01-08 15:52 ` Daniel Jacobowitz
2007-01-08 16:02 ` Ulrich Weigand
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=200701081547.l08Fler8026574@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.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