This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Testsuites
- To: David dot Billinghurst at riotinto dot com dot au, mark at codesourcery dot com
- Subject: RE: Testsuites
- From: Mike Stump <mrs at windriver dot com>
- Date: Mon, 5 Jun 2000 16:39:52 -0700 (PDT)
- Cc: gcc at gcc dot gnu dot org
> To: David.Billinghurst@riotinto.com.au
> Cc: gcc@gcc.gnu.org
> From: Mark Mitchell <mark@codesourcery.com>
> Date: Sun, 04 Jun 2000 17:05:00 -0700
> >>>>> "Billinghurst," == Billinghurst, David (CRTS) <David.Billinghurst@riotinto.com.au> writes:
> Billinghurst,> A couple of questions: * How do you mark a g77 test
> Billinghurst,> as XFAIL * How do you do it for a particular target
> Good questions. I do not have the answer. If anyone knows, it would
> be valuable to contribute some HTML for the web pages.
Actually, Fortran was one of the few that had 0 unexpected failures.
:-( Then someone broke it, and I've never seen it recover. Now, me I
would have two branches, and test code on the development branch, and
if it tests well (automated), then move it en mass to the release
branch. The idea then is no code could ever be in this branch that
didn't test well. Development in progress, then would be on the other
branch. People want their code in a release, you have to get it to
pass. Note, getting a pass, just means marking new failures as
expected, if in your value judgment the compiler is better off with
the work, than without.