From: Dave Lee <davel@canuck.com>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] gcc 3.1 inconsistencies :
Date: Tue, 4 Jun 2002 21:22:07 -0600 [thread overview]
Message-ID: <Pine.SGI.4.21.0206042056110.27878136-100000@the-gimp> (raw)
In-Reply-To: <20020605032351.4194bfa6.spider@gentoo.org>
Spider wrote:
> soo, right now I'm running march=athlon-tbird -O3 -pipe for most things
In case anybody is curious like I was:
I didn't know the difference between the various athlon arch settings,
athlon-tbird, athlon-xp, etc. I found that there are two athlon
variations, those with the sse instruction set and those w/o sse.
no sse: athlon, athlon-tbird
sse: athlon-4, athlon-xp, athlon-mp
`grep sse /proc/cpuinfo` to see if your cpu has sse, though I don't know
how reliable cpuinfo is. I have a duron 1GHz, and it has sse, but earlier
durons, <1GHz, don't have sse.
also, when you do either of -msse -m3dnow gcc automagically does -mmmmx
for you.
from what I see, athlon and athlon-tbird are identical arch settings, as
are athlon-4, athlon-xp, and athlon-mp.
so can anyone verify this? of course its possible the different names are
there for finer grained code gen in the future.
Dave
next prev parent reply other threads:[~2002-06-05 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 1:23 [gentoo-dev] gcc 3.1 inconsistencies : Spider
2002-06-05 3:22 ` Dave Lee [this message]
2002-06-05 5:00 ` fthieme
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=Pine.SGI.4.21.0206042056110.27878136-100000@the-gimp \
--to=davel@canuck.com \
--cc=gentoo-dev@gentoo.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