From: waltdnes@waltdnes.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cpu flags / USE flags / compiler flags
Date: Sat, 3 Sep 2005 23:27:19 -0400 [thread overview]
Message-ID: <20050904032719.GA6185@waltdnes.org> (raw)
In-Reply-To: <5bdc1c8b05083109046b8ebdf7@mail.gmail.com>
On Wed, Aug 31, 2005 at 09:04:21AM -0700, Mark Knecht wrote
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
> xtpr
[...deletia...]
> I then looked for CPU flags that had an equivalent USE flag and that
> might be of use for faster graphics. On this machine I chose mmx, sse
> & sse2. Armed with that I changed my make.conf file to look like this:
There are CPU flags and there are USE flags. Some of them have the
same names, and that may confuse you. It works like this...
1) Get a listing of your cpu's flags in /proc/cpuinfo
2) Check against the list of supported flags in gcc for you cpu, and
add them to CFLAGS
3) Check http://www.gentoo.org/dyn/use-index.xml for a list of valid
USE flags, and include any that show up in /proc/cpuinfo
4) Repeat step 3) with /usr/portage/profiles/use.local.desc for any
programs you're emerging. There doesn't seem to be anything
special on your pentium4, but my AMD64 not only has mmx and 3dnow,
it also has mmxext and 3dnowext. mplayer can take advantage of
them. I include them in the /etc/portage/package.use entry for
media-video/mplayer.
I'll assume that you're using gcc 3.3.5. In that case, the place to
look for CPU flag options is...
http://gcc.gnu.org/onlinedocs/gcc-3.3.5/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
That list shows pentium4, mmx, sse, and sse2. Also, if you have *ANY*
version of sse available, you can improve performance by running floating
point math via sse, rather than 387 instructions. I recommend...
CFLAGS="-O2 -pipe -fomit-frame-pointer -march=pentium4 -mmmx -msse -msse2 -mfpmath=sse"
http://www.gentoo.org/dyn/use-index.xml shows mmx and sse as valid USE
flags, so you can include them in USE.
--
Walter Dnes <waltdnes@waltdnes.org>
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-04 3:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 16:04 [gentoo-user] cpu flags / USE flags / compiler flags Mark Knecht
2005-08-31 16:52 ` Volker Armin Hemmann
2005-08-31 17:21 ` Mark Knecht
2005-08-31 18:44 ` Volker Armin Hemmann
2005-08-31 19:07 ` capsel
2005-09-04 3:27 ` waltdnes [this message]
2005-09-04 5:18 ` Mark Knecht
2005-09-04 6:11 ` ellotheth rimmwen
2005-09-04 6:21 ` Volker Armin Hemmann
2005-09-04 12:45 ` Mark Knecht
2005-09-05 1:59 ` waltdnes
2005-09-06 3:25 ` Bob Sanders
2005-09-06 3:35 ` Mark Knecht
2005-09-06 4:04 ` Bob Sanders
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=20050904032719.GA6185@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