From: "Sami Näätänen" <sn.ml@keijukammari.fi>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] CFLAGS question from a AMD64 newbie
Date: Tue, 9 Dec 2008 14:23:30 +0200 [thread overview]
Message-ID: <200812091423.30562.sn.ml@keijukammari.fi> (raw)
So hi from a amd64 newbie. Not so newbie with Gentoo though. :)
My system is an Intel quad core core2 with a 2.4 GHz clock speed coupled with
a 4GB of memory. No overclocking etc. Want this to be stable. :)
I'm just curious what people use as their stable CFLAGS in amd64 Gentoo?
(Sorry if this has been up lately, but I just switched to 64bit env so...)
Here is mine and some explanation of why (And I use ~arch system with gcc 4.3)
The flags are in order they are used in my CFLAGS and CXXFLAGS.
Gives stable base
-O2
Want to optimize for my system, but don't want "native"
-march=core2
If some ebuilds filter march this will still cache optimize etc for my system
-mtune=core2
Faster floating point math and better chance of vectorization
-mfpmath=sse
These because of the march might get filtered
-mmmx -msse -msse2 -msse3 -mssse3
For loop vectorization
-ftree-vectorize
Just to get some Idea how much vectorized loops there will be.
By the way I surprised the amount of "LOOP VECTORIZED" notes in the compile
output. And only have seen couple of two versions
-ftree-vectorizer-verbose=1
Of course I don't want temp files :)
-pipe
I don't use any loop unrolling etc, because it would only add the code size.
I'm not so brave that I would dare to use -Os.
So what's your experiences and reasoning behind what you do?
Any benchmarks or so?
PS. If you see same post without this added postscript. Just ignore it, it's
the same post, but I forgot to change my default identity for this ML.
next reply other threads:[~2008-12-09 12:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 12:23 Sami Näätänen [this message]
2008-12-09 13:13 ` [gentoo-amd64] CFLAGS question from a AMD64 newbie Martin Herrman
2008-12-09 14:15 ` Branko Badrljica
2008-12-09 15:33 ` [gentoo-amd64] " Duncan
2008-12-09 13:28 ` [gentoo-amd64] " Volker Armin Hemmann
2008-12-09 19:59 ` Sami Näätänen
2008-12-10 7:00 ` Branko Badrljica
2008-12-10 7:27 ` Volker Armin Hemmann
2008-12-09 16:07 ` [gentoo-amd64] " Duncan
2008-12-09 17:40 ` Branko Badrljica
2008-12-09 20:34 ` Sami Näätänen
2008-12-10 7:35 ` Duncan
2008-12-16 23:00 ` Branko Badrljica
2008-12-16 22:46 ` Duncan
2008-12-17 2:00 ` Branko Badrljica
2008-12-17 8:41 ` Duncan
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=200812091423.30562.sn.ml@keijukammari.fi \
--to=sn.ml@keijukammari.fi \
--cc=gentoo-amd64@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