From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4/2.5] Athlon CFLAGS
Date: Mon, 9 Sep 2002 02:46:45 +0200 [thread overview]
Message-ID: <20020909004644.GA21949@debian> (raw)
In-Reply-To: <200209090213.10063.daniel.mehrmann@gmx.de>
in your patch, you don't check the gcc version.
if i run with a gcc-2.95.3, you will be a compile error
On Mon, Sep 09, 2002 at 02:13:10AM +0200, Daniel Mehrmann wrote:
> On Monday 09 September 2002 01:18, 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
>
> Hi Dave,
>
> yes, you`re right with the athlon-4 option. Well, first thing, the mobile athlon
> have the same core as XP (Palomino) expect some "speed scheudle".
> I never see that we support mobile chips. So i think it`s enough that we
> put Athlon4 into the "XP group". I think too the new core "Thoroughbread"
> should use the "XP group".
>
> I readed the gcc documentation, gcc-3.2 only, very deep. This was the idea for this patch.
> Then i looked fast into gcc-3.1/3.0/2.95x. I believe that the compiler create own code
> for *every* chip-release. chip-release as: athlon-tbird, athlon-xp, ...
>
> Also take a look into the binary code and size. It`s different.
>
> chears,
> Daniel
>
>
>
>
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Stephane Wirtel <stephane.wirtel@belgacom.net>
Web : www.linux-mons.be "Linux Is Not UniX !!!"
next prev parent reply other threads:[~2002-09-09 0:42 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 [this message]
2002-09-09 1:07 ` Daniel Mehrmann
2002-09-09 0:37 ` Jeff Garzik
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=20020909004644.GA21949@debian \
--to=stephane.wirtel@belgacom.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox