public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rwhaley@cs.utk.edu
Subject: Re: c/3913: On Athlon's, gcc 3.0 produces code running 1/2 as fast as gcc 2.95
Date: Wed, 24 Apr 2002 14:41:00 -0000	[thread overview]
Message-ID: <20020424214131.18261.qmail@sources.redhat.com> (raw)

Synopsis: On Athlon's, gcc 3.0 produces code running 1/2 as fast as gcc 2.95

State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Wed Apr 24 14:41:30 2002
State-Changed-Why:
    From the web page:
    
    NOTE: all of these problems appear to be fixed in the newer 3.1 preleases. I tested gcc-20020225.tar.gz, and found it performed indistinguishably from 2.95.2 for both Athlon and PIII. An ATLAS user has independently verified this observation for PIII/P4.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3913


             reply	other threads:[~2002-04-24 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 14:41 rth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-01 17:56 rwhaley

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=20020424214131.18261.qmail@sources.redhat.com \
    --to=rth@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rwhaley@cs.utk.edu \
    /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).