public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@cs.tu-berlin.de>
To: ebotcazou@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9279: [3.2 regression] [Sparc] combine bug
Date: Tue, 28 Jan 2003 22:36:00 -0000	[thread overview]
Message-ID: <20030128223601.18893.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/9279; it has been noted by GNATS.

From: Matthias Klose <doko@cs.tu-berlin.de>
To: Gabriel Dos_Reis <gdosreis@sophia.inria.fr>
Cc: Eric Botcazou <ebotcazou@libertysurf.fr>, ebotcazou@gcc.gnu.org,
        frank@g-n-u.de, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/9279: [3.2 regression] [Sparc] combine bug
Date: Tue, 28 Jan 2003 23:28:20 +0100

 Gabriel Dos_Reis writes:
 > | Eric Botcazou writes:
 > | > >     The fix introduces a performance regression for PowerPC (and possibly
 > | > > other platforms) on the 3.2 branch.
 > | > 
 > | > Now reverted for this reason on the 3.2 branch so GCC 3.2.2 will ship with 
 > | > the bug.
 > | 
 > | I see you having the choice between two regressions, one performance
 > | regression (from 3.2.1 to 3.2.2) and one "wrong code" regression (from
 > | 2.95 and 3.0.4 to 3.2.2). Not sure, if I should like your decision.
 > 
 > As I explained to Eric, I would have been pleased to apply that
 > patch.  However it turned out that it introduces (1) a performance
 > regression; (2) possibly a wrong code generation -- David gave some
 > references.  Therefore, to fix the new regressions we would have to grab 
 > other patches not known to be safe.  The initial patch was beginning
 > to have too much ramifications.  That is why I asked Eric to revert
 > his patch.
 
 Thanks for the clarification, I did miss this information on the gnats
 report.


             reply	other threads:[~2003-01-28 22:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 22:36 Matthias Klose [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-16 15:00 ebotcazou
2003-01-29  1:36 Gabriel Dos_Reis
2003-01-29  1:26 Gabriel Dos_Reis
2003-01-29  0:06 Christian Ehrhardt
2003-01-28 23:36 Eric Botcazou
2003-01-28 22:16 Gabriel Dos_Reis
2003-01-28 20:56 Matthias Klose
2003-01-27 17:56 Eric Botcazou
2003-01-27 17:05 ebotcazou
2003-01-25 16:12 ebotcazou
2003-01-24 16:27 ebotcazou
2003-01-24 11:06 Christian Ehrhardt
2003-01-23 19:44 ebotcazou

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=20030128223601.18893.qmail@sources.redhat.com \
    --to=doko@cs.tu-berlin.de \
    --cc=ebotcazou@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    /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).