From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, jimb@zwingli.cygnus.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com, kevinb@redhat.com
Subject: Re: [RFA/c++] Fix printing classes with virtual base classes
Date: Thu, 15 Nov 2001 14:06:00 -0000 [thread overview]
Message-ID: <200111280438.WAA13847@duracef.shout.net> (raw)
And I would be happy to run tests against v2 and v3 C++ compilers
and report the results. Most of my time is only on weekends though.
The trouble with the gdb C++ code is that it's not logic bugs, it's
perverse data structures where each bug fix may not affect the
test results much. So Jim's judgement is much more useful than
my mechanical test results.
Michael C
WARNING: multiple messages have this Message-ID
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, jimb@zwingli.cygnus.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com, kevinb@redhat.com
Subject: Re: [RFA/c++] Fix printing classes with virtual base classes
Date: Tue, 27 Nov 2001 20:38:00 -0000 [thread overview]
Message-ID: <200111280438.WAA13847@duracef.shout.net> (raw)
Message-ID: <20011127203800.1kbrcrPLbiwuM7UCz30wuxSdTZJwFpbZgDMIdIdI8eM@z> (raw)
And I would be happy to run tests against v2 and v3 C++ compilers
and report the results. Most of my time is only on weekends though.
The trouble with the gdb C++ code is that it's not logic bugs, it's
perverse data structures where each bug fix may not affect the
test results much. So Jim's judgement is much more useful than
my mechanical test results.
Michael C
next reply other threads:[~2001-11-28 4:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 14:06 Michael Elizabeth Chastain [this message]
2001-11-16 11:52 ` Daniel Berlin
2001-11-27 20:49 ` Daniel Berlin
2001-11-27 20:38 ` Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 9:00 Michael Elizabeth Chastain
2001-11-21 23:07 ` Michael Elizabeth Chastain
2001-11-22 3:17 ` Daniel Jacobowitz
2001-11-30 9:52 ` Daniel Jacobowitz
2001-11-13 9:24 Daniel Jacobowitz
2001-11-13 9:24 ` Daniel Jacobowitz
2001-11-13 9:34 ` Kevin Buettner
2001-11-26 18:25 ` Kevin Buettner
2001-11-26 21:07 ` Andrew Cagney
2001-11-13 21:56 ` Andrew Cagney
2001-11-14 22:09 ` Jim Blandy
2001-11-27 12:48 ` Jim Blandy
2001-11-26 18:02 ` Daniel Jacobowitz
2001-11-13 18:02 ` Jim Blandy
2001-11-14 9:33 ` Daniel Jacobowitz
2001-11-14 22:39 ` Jim Blandy
2001-11-14 22:41 ` Daniel Jacobowitz
2001-11-27 13:26 ` Daniel Jacobowitz
2001-11-21 13:03 ` Daniel Jacobowitz
2001-11-22 13:53 ` Jim Blandy
2001-11-30 11:42 ` Jim Blandy
2001-11-29 22:41 ` Daniel Jacobowitz
2001-11-30 8:48 ` Andrew Cagney
2001-11-21 17:30 ` Andrew Cagney
2001-11-30 8:57 ` Daniel Jacobowitz
2001-11-21 23:07 ` Daniel Jacobowitz
2001-11-27 13:16 ` Jim Blandy
2001-11-26 23:08 ` Daniel Jacobowitz
2001-11-26 20:38 ` Jim Blandy
2001-11-26 21:36 ` Daniel Jacobowitz
2001-11-14 0:12 ` Daniel Jacobowitz
2001-11-26 22:05 ` Daniel Berlin
2001-11-14 0:15 ` Daniel Berlin
2001-11-27 7:15 ` Jim Blandy
2001-11-14 13:02 ` Jim Blandy
2001-11-27 7:45 ` Daniel Jacobowitz
2001-11-14 13:55 ` Daniel Jacobowitz
2001-11-26 17:19 ` Daniel Jacobowitz
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=200111280438.WAA13847@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.com \
--cc=kevinb@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