public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: ebotcazou@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9319: slower code generated for simple loop on linux
Date: Thu, 16 Jan 2003 19:16:00 -0000	[thread overview]
Message-ID: <20030116191604.10064.qmail@sources.redhat.com> (raw)

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

From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Amnon Cohen <amnon_cohen@yahoo.com>
Cc: Richard Henderson <rth@redhat.com>,
 gcc-bugs@gcc.gnu.org,
 gcc-prs@gcc.gnu.org,
 nobody@gcc.gnu.org,
 gcc-gnats@gcc.gnu.org
Subject: Re: optimization/9319: slower code generated for simple loop on linux
Date: Thu, 16 Jan 2003 20:12:03 +0100

 > I have done a few more tests, and it seems
 > that this is a regression
 > on all platforms  (not just intel) introduced by
 > gcc3.1
 
 Confirmed. The regression actually started to show up in gcc 3.0.4 (that'=
 s why=20
 I asked you to post the assembly code, I only had the 3.0.4 version on my=
 =20
 system) and has affected all versions since then.
 
 > The performance is significantly reduced on intel
 > linux and on Solaris (I have not sent solaris asm
 > files, let me know if you need them). So I do
 > not think that this is architecture related
 
 A nasty side-effect of the patch that fixed PR optimization/5076, which w=
 as=20
 foreseen by Richard: http://gcc.gnu.org/ml/gcc-patches/2002-01/msg02111.h=
 tml
 
 Richard, do you think that the problem is worth looking into or that it i=
 s a=20
 lost cause ?
 
 --=20
 Eric Botcazou


             reply	other threads:[~2003-01-16 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 19:16 Eric Botcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16  7:09 ebotcazou
2003-01-22  2:06 Richard Henderson
2003-01-21 23:16 Eric Botcazou
2003-01-17  9:35 ebotcazou
2003-01-17  3:36 Richard Henderson
2003-01-16 13:36 Amnon Cohen
2003-01-16 11:58 ebotcazou
2003-01-15 10:16 amnon_cohen

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=20030116191604.10064.qmail@sources.redhat.com \
    --to=ebotcazou@libertysurf.fr \
    --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).