From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: Remove some spurious test fails
Date: Sat, 10 Jun 2006 00:09:00 -0000 [thread overview]
Message-ID: <20060610000933.GD860@adacore.com> (raw)
In-Reply-To: <20060609190957.GA5616@nevyn.them.org>
> > Although it would be good to fix gcc, that's not practical right now, and I
> > thought it would be better to defensively code the gdb testsuite anyway.
>
> Anyone else have an opinion on this? I think it's reasonable to avoid
> problematic constructs and test for them explicitly
I agree with Nathan too. In fact, I'm starting to reallly like "pure"
testcases were we only test as few as possible different things. I don't
want one side issue polluting the results of a given testcase...
--
Joel
next prev parent reply other threads:[~2006-06-10 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 15:28 Nathan Sidwell
2006-06-09 19:10 ` Daniel Jacobowitz
2006-06-10 0:09 ` Joel Brobecker [this message]
2006-06-13 13:31 ` Nathan Sidwell
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=20060610000933.GD860@adacore.com \
--to=brobecker@adacore.com \
--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