public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Luigi Genoni <kernel@Expansa.sns.it>
Cc: "Paul G. Allen" <pgallen@randomlogic.com>,
	"Linux kernel developer's mailing list" 
	<linux-kernel@vger.kernel.org>,
	gcc@gcc.gnu.org
Subject: Re: gcc-2.95.3 vs gcc-3.0.4
Date: Mon, 25 Feb 2002 04:59:00 -0500	[thread overview]
Message-ID: <20020225045859.S2434@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020225024817.Q2434@devserv.devel.redhat.com> <Pine.LNX.4.44.0202251044040.18205-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.44.0202251044040.18205-100000@Expansa.sns.it>; from kernel@Expansa.sns.it on Mon, Feb 25, 2002 at 10:46:52AM +0100

On Mon, Feb 25, 2002 at 10:46:52AM +0100, Luigi Genoni wrote:
> > > At this link:
> > >
> > >  http://www.cs.utk.edu/~rwhaley/ATLAS/gcc30.html
> > >
> > > you can find an interesting explanation why code compiled with gcc 3.0 is
> > > mostly slower than code compiled with gcc 2.95 on x86 CPUs (but it is
> > > really faster on other platforms like alpha and sparc64).
> > >
> > > basically the main reasons semm to be the scheduler algorithm and the fpu
> > > stack handling, but I suggest to read the full study.
> > >
> > >
> > > I would be interested to know if this apply to gcc 3.1 too.
> >
> > Well, concerning reg-stack, you can completely get away without it in 3.1
> > by using -mfpmath=sse if you are targeting Pentium 3,4 or Athlon 4,xp,mp
> > (for float math, for higher precision only for Pentium 4).
> 
> Yes, but the lot of users (like me) who are still using Athlon TB, 1330 or
> 1400 Mhz, and who do not have any reason to upgrade to MP since the
> performance gain is not really considerable, they cannot use sse instructions.
> So, what could they do? should they stay with gcc 2.95?

Linux kernel doesn't use floating point math at all, so this is irrelevant
on lkml, moving to an more appropriate list...

	Jakub

  reply	other threads:[~2002-02-25  9:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  4:40 gcc-2.95.3 vs gcc-3.0.4 Justin Piszcz
2002-02-23  4:44 ` Larry McVoy
2002-02-23  5:13   ` Justin Piszcz
2002-02-23  5:22   ` Andrew Morton
2002-02-23  5:50     ` Richard Gooch
2002-02-23 10:31     ` Benny Sjostrand
2002-02-23 15:00     ` Martin Dalecki
2002-02-25  8:07     ` Simon Kirby
2002-02-25  8:15       ` David S. Miller
2002-02-25  8:32       ` David Rees
2002-02-25  9:32         ` Ian Castle
2002-02-25  9:52       ` Markus Schaber
2002-02-23  5:40 ` hugang
2002-02-23  5:56   ` Andrew Morton
2002-02-23  9:25     ` Paul G. Allen
2002-02-23 13:55       ` gmack
2002-02-23 15:43       ` bert hubert
2002-02-25  0:07       ` Luigi Genoni
2002-02-25  0:32         ` ANN: syscalltrack v0.7 released guy keren
2002-02-25  7:48         ` gcc-2.95.3 vs gcc-3.0.4 Jakub Jelinek
2002-02-25  9:46           ` Luigi Genoni
2002-02-25  9:59             ` Jakub Jelinek [this message]
2002-02-25 12:55               ` Jan Hubicka
2002-02-25 16:08 ` Juan Quintela

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=20020225045859.S2434@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kernel@Expansa.sns.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgallen@randomlogic.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