public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: mstump@apple.com, gcc@gcc.gnu.org
Subject: Re: A testcase library
Date: Tue, 24 Dec 2002 12:30:00 -0000	[thread overview]
Message-ID: <ro1bs3bfii9.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <10212240139.AA22944@vlsi1.ultra.nyu.edu>

On Mon, 23 Dec 02 20:39:06 EST, kenner@vlsi1.ultra.nyu.edu (Richard Kenner) said:

> Indeed can somebody explain what the diffence is between an "expected"
> failure and a "known" failure?  Intuitively, they sound the same to me.

Yeah, the naming is a little weird.  These days I think of the X in
XFAIL as standing for "external" rather than "expected".

David Carlton
carlton@math.stanford.edu

  reply	other threads:[~2002-12-24 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 18:08 Richard Kenner
2002-12-24 12:30 ` David Carlton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-23 18:42 Richard Kenner
2002-12-23 21:57 ` Daniel Jacobowitz
2002-12-24 12:28 ` David Carlton
2002-12-20  8:12 Volker Reichelt
2002-12-20  8:14 ` Jakub Jelinek
2002-12-20  8:50   ` Volker Reichelt
2002-12-20  9:12     ` Eric Botcazou
2002-12-20  9:32       ` Wolfgang Bangerth
2002-12-20 10:51         ` Volker Reichelt
2002-12-20 12:02     ` Jason R Thorpe
2002-12-22 22:44     ` Ben Elliston
2002-12-23 12:46       ` Mike Stump
2002-12-23 12:57         ` Daniel Jacobowitz
2002-12-23 15:54           ` Mike Stump
2002-12-23 16:35             ` Daniel Jacobowitz
2002-12-23 13:50         ` Ben Elliston
2002-12-23 14:00           ` Zack Weinberg
2002-12-23 15:27             ` Daniel Jacobowitz
2002-12-20 15:01   ` Joseph S. Myers

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=ro1bs3bfii9.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    --cc=mstump@apple.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).