From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: branch comparison tables
Date: Fri, 23 Jan 2004 00:43:00 -0000 [thread overview]
Message-ID: <20040123004352.GA21031@nevyn.them.org> (raw)
In-Reply-To: <20040122230758.B60AB4B104@berman.michael-chastain.com>
On Thu, Jan 22, 2004 at 06:07:58PM -0500, Michael Chastain wrote:
> Here are some new tables:
>
> http://www.shout.net/~mec/sunday/2004-01-19-branch
>
> This is all four branches (6.0, HEAD, carlton_dictionary-branch,
> drow-cplus-branch) run with the test suite from gdb HEAD.
> So the compare-by-gdb tables are actually useful here.
>
> Looking at compare-by-gdb, at the sub-tables with "as=2.14, ld=2.14".
> There is not a lot of variation based on the version of binutils.
> So sub-tables #2 #3 #6 #7 #10 #11 #16 #17 #22 #23 #28 #29 ought to
> cover all the interesting information.
>
> I would like to do more of this. Conceptually, I've got it worked out
> that the version of the gdb test suite and the version of gdb are
> independent attributes of a test run. I just have to figure out how to
> present it usefully, and then write some more Perl.
Neat.
By the way, FYI: At this moment, the FAILs (only, not looking at the
kfails at the moment) for GCC 3.4 and GCC HEAD are in several
categories:
- gdb bugs
- testsuite bugs
- java tests, blah
- namespace issue that David is looking at
I believe that no more of them are caused by GCC. The
multi_line_while_statement failures in your tables were, but I checked
in a fix this morning.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-23 0:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 23:08 Michael Elizabeth Chastain
2004-01-23 0:43 ` Daniel Jacobowitz [this message]
2004-01-23 3:39 Michael Elizabeth Chastain
2004-01-23 5:01 ` 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=20040123004352.GA21031@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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