From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dave Jones <davej@suse.de>
Cc: Daniel Mehrmann <daniel.mehrmann@gmx.de>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4/2.5] Athlon CFLAGS
Date: Sun, 08 Sep 2002 20:37:01 -0400 [thread overview]
Message-ID: <3D7BED2D.8000705@mandrakesoft.com> (raw)
In-Reply-To: 20020909011833.B14358@suse.de
Dave Jones wrote:
> On Sun, Sep 08, 2002 at 09:28:11PM +0200, Daniel Mehrmann wrote:
> > Hi Alan,
> >
> > i add for the AMD Athlon family some optimize compilerflags.
> > Gcc 3.1 and 3.2 support more specific Athlon instructions as 3.0 or 2.95x.
> > This patch for 2.4.19, 2.4.20-pre5 and 2.5.33 set a new "-march" flag:
> >
> > Athlon TB/Duron += -march=athlon-tbird
> > Athlon XP/Athlon4/Duron += -march=athlon-xp
> > Athlon MP += -march=athlon-mp
>
> I thought these were all just gcc aliases for the same options ?
> It's been a while since I looked at the gcc option parser, so I've
> forgotten exactly what happens, but at least you missed the
> bogus athlon-4 option.
>
> Are the gains between all these options really worth the added
> complexity ?
>
> Dave
>
They all have the same scheduling AFAICS, there are minor variations
between athlon, athlon-tbird, and the rest:
>
> {"athlon", PROCESSOR_ATHLON, PTA_MMX | PTA_PREFETCH_SSE | PTA_3DNOW
> | PTA_3DNOW_A},
> {"athlon-tbird", PROCESSOR_ATHLON, PTA_MMX | PTA_PREFETCH_SSE
> | PTA_3DNOW | PTA_3DNOW_A},
> {"athlon-4", PROCESSOR_ATHLON, PTA_MMX | PTA_PREFETCH_SSE | PTA_3DNOW
> | PTA_3DNOW_A | PTA_SSE},
> {"athlon-xp", PROCESSOR_ATHLON, PTA_MMX | PTA_PREFETCH_SSE | PTA_3DNOW
> | PTA_3DNOW_A | PTA_SSE},
> {"athlon-mp", PROCESSOR_ATHLON, PTA_MMX | PTA_PREFETCH_SSE | PTA_3DNOW
> | PTA_3DNOW_A | PTA_SSE},
prev parent reply other threads:[~2002-09-09 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 19:28 [PATCH 2.4/2.5] Athlon CFLAGS Daniel Mehrmann
2002-09-08 23:18 ` Dave Jones
2002-09-09 0:13 ` Daniel Mehrmann
2002-09-09 0:46 ` Stephane Wirtel
2002-09-09 1:07 ` Daniel Mehrmann
2002-09-09 0:37 ` Jeff Garzik [this message]
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=3D7BED2D.8000705@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=daniel.mehrmann@gmx.de \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.