public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: mrs@wrs.com (Mike Stump)
Cc: richard.earnshaw@arm.com, egcs@cygnus.com, rearnsha@sun52.arm.com
Subject: Re: Will the consistent failures in EGCS be fixed soon?
Date: Mon, 29 Jun 1998 20:41:00 -0000	[thread overview]
Message-ID: <15205.899177839@hurl.cygnus.com> (raw)
In-Reply-To: <199806292135.OAA10101@kankakee.wrs.com>

  In message < 199806292135.OAA10101@kankakee.wrs.com >you write:
  > Yes, they should be.  As Jeff pointed out, they don't have the
  > infrastructure to mark them precisely.  I think the should be marked
  > as precisely as possible.  Or put another way, we should xfail the
  > entire series of sets and have a few extra XPASSes that we can't get
  > rid of, then a few unexpected fails that we can't get ride of.
Or we just fix the bugs.  I'd be game for xfailing anything from before
1998 (ie the loop-* and some of the varargs/stdarg cases).  I'd
prefer to hold off on newer tests since we do have folks working on
fixing them.

jeff

  reply	other threads:[~1998-06-29 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-29 19:43 Mike Stump
1998-06-29 20:41 ` Jeffrey A Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-06-29 19:00 Mike Stump
1998-06-23 21:11 Benjamin Redelings I
1998-06-24 10:08 ` Horst von Brand
1998-06-24 15:17 ` Martin von Loewis
1998-06-25  0:25 ` Jeffrey A Law
1998-06-24 17:12   ` Benjamin Redelings I
1998-06-25  6:50   ` Richard Earnshaw
1998-06-25  9:25     ` Jeffrey A Law
1998-06-25 12:33       ` Richard Earnshaw
1998-06-25 15:59         ` Jeffrey A Law
1998-06-26 13:03         ` Carlo Wood
1998-06-26 13:03           ` Richard Earnshaw

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=15205.899177839@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=mrs@wrs.com \
    --cc=rearnsha@sun52.arm.com \
    --cc=richard.earnshaw@arm.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).