public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: patch/RFC: PR optimization/8423
Date: Wed, 06 Nov 2002 11:33:00 -0000	[thread overview]
Message-ID: <20021106193340.GA26150@tornado.toronto.redhat.com> (raw)
In-Reply-To: <20021106192337.GI22066@redhat.com>

On Wed, 06 Nov 2002, Richard Henderson wrote:

> Failing improvements in both compile quality and compile time,
> I think we should simply xfail this test.
> 
Well no, don't XFAIL it.  The test passes just fine, on tree-ssa  ;)

  reply	other threads:[~2002-11-06 19:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 13:55 Zack Weinberg
2002-11-06 11:23 ` Richard Henderson
2002-11-06 11:33   ` Diego Novillo [this message]
2002-11-06 14:34     ` Richard Henderson
2002-11-06 11:36   ` Zack Weinberg
2002-11-06 14:33     ` Richard Henderson
2002-11-06 15:01       ` Zack Weinberg
2002-11-06 15:07         ` Richard Henderson
2002-11-07  3:06       ` Michael Matz
2002-11-05 16:17 Roger Sayle

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=20021106193340.GA26150@tornado.toronto.redhat.com \
    --to=dnovillo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.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).