From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] mmx use flag on Pentium 4
Date: Sun, 25 Sep 2005 00:13:36 -0400 [thread overview]
Message-ID: <20050925041336.GA20429@waltdnes.org> (raw)
In-Reply-To: <4335CEDB.7080707@djnauk.co.uk>
On Sat, Sep 24, 2005 at 11:10:35PM +0100, Jonathan Wright wrote
> however since that version -mcpu has been depreciated in favor for -mtune.
I use -march, so that point is moot.
> As for the mmx information, that's valid across all gcc versions. If
> you specify -march=pentium4 and -mcpu=pentium4 as part of your
> CFLAGS, -mmmx and -msse, etc., will be implied by the compiler,
> and any programs built to take advantage of the extensions will be
> able to do so.
The docs for 3.4.X are a lot more detailed than 3.3.X docs. 3.3.6
docs say that -march implies -mcpu but don't say in so many words that
certain values of -march imply -sse, etc.
While we're talking about compilers and sparse documentation, I've got
an AMD64 K8. The docs for an AMD64-bit install scared me off to 32-bit
land. Later I found out that the 64-bit install docs are out-of-date
and the problems they mention seem to have been solved. However, since
I have things humming along, I don't really want to tear my install down
and rebuild from scratch. One question... I'm running
> CFLAGS="-O2 -pipe -fomit-frame-pointer -march=athlon -m3dnow -mmmx -msse -msse2 -mfpmath=sse"
Is there a way to figure out if I can use a higher version of Athlon
in my CFLAGS line in 32-bit mode?
--
Walter Dnes <waltdnes@waltdnes.org>
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-09-25 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 20:32 [gentoo-user] mmx use flag on Pentium 4 Robert Persson
2005-09-24 20:45 ` Jonathan Wright
2005-09-24 21:55 ` Walter Dnes
2005-09-24 22:10 ` Jonathan Wright
2005-09-25 4:13 ` Walter Dnes [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=20050925041336.GA20429@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.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