public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: law@cygnus.com
Cc: rearnsha@sun52.arm.com, egcs@cygnus.com
Subject: Re: Will the consistent failures in EGCS be fixed soon?
Date: Thu, 25 Jun 1998 06:50:00 -0000	[thread overview]
Message-ID: <199806251153.MAA14147@sun52.NIS.cambridge> (raw)
In-Reply-To: <25494.898733105@hurl.cygnus.com>

> The loop* things aren't likely to be addressed anytime soon.  They
> are horribly obscure problems that nobody is likely to ever trigger
> unless they go look at the gcc source code and specifically write
> code to trigger a specific problem in the loop optimizer.
> 
> There's also an alias bug in the testsuite that we aren't actively
> working on, but we do want to keep the test because we do want to
> fix the problem at some point.
> 

So shouldn't these be marked as XFAILs?  Then I won't waste time looking 
into the failure in case it is a port problem.

Richard.


  parent reply	other threads:[~1998-06-25  6:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
1998-06-29 19:00 Mike Stump
1998-06-29 19:43 Mike Stump
1998-06-29 20:41 ` Jeffrey A Law

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=199806251153.MAA14147@sun52.NIS.cambridge \
    --to=rearnsha@arm.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=rearnsha@sun52.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).