From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: A testsuite update, for the curious
Date: Tue, 14 Jan 2003 17:36:00 -0000 [thread overview]
Message-ID: <200301141736.h0EHaX105244@duracef.shout.net> (raw)
Hi Daniel,
We're in danger here of doing partial analysis on a lot of bugs
and not finishing any of them. Well, okay, I'm in that danger.
You get a lot of stuff committed. :)
> It is dependent (like the rest of gdb.gdb/) on the compiler used to
> build gdb and the optimization level. Do you use 2.95.3 +
> optimization to build any of your GDB's?
I don't control any optimization dimension, so all my tests are
at default optimization. So that explains why you see stuff in
complaints.exp and I don't see it.
I do test with many gcc's including gcc 2.95.3.
I could really use a big home cluster!
Michael C
next reply other threads:[~2003-01-14 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 17:36 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 8:19 Michael Elizabeth Chastain
2003-01-14 17:26 ` Daniel Jacobowitz
2003-01-14 5:04 Daniel Jacobowitz
2003-01-14 6:50 ` Daniel Jacobowitz
2003-01-14 7: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=200301141736.h0EHaX105244@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@sources.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