| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
CFLAGS is something you can easily break a system with, no matter what |
| 5 |
compiler version. You should read up on any flag before applying it and |
| 6 |
be very conservative on production systems / systems that you need and |
| 7 |
that should always be in a working condition. |
| 8 |
|
| 9 |
I have those CFLAGS on various systems: |
| 10 |
Production server running amd64 and gcc-3.4.5: |
| 11 |
CFLAGS="-O2 -march=k8 -pipe -fomit-frame-pointer -msse3" |
| 12 |
CXXFLAGS="${CFLAGS}" |
| 13 |
|
| 14 |
Home server running x86 and gcc-4.1.1: |
| 15 |
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe -mmmx -m3dnow |
| 16 |
- -msse -mfpmath=sse" |
| 17 |
CXXFLAGS=${CFLAGS} |
| 18 |
|
| 19 |
Desktop machine running ~amd64 and gcc-4.1.1 (my box for testing, |
| 20 |
experimenting and generally messing around with stuff): |
| 21 |
CFLAGS="-O2 -march=k8 -fomit-frame-pointer -pipe -msse3" |
| 22 |
CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden" |
| 23 |
|
| 24 |
|
| 25 |
There's a thread called "CFLAGS central" on forums.gentoo.org where |
| 26 |
discussions about CFLAGS take place. It's long, it's sometimes very |
| 27 |
controversial, but it's also quite informing. General rule of thumb: If |
| 28 |
you don't know exactly what you are doing you shouldn't be doing it ^^ |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.4.2.2 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 32 |
|
| 33 |
iD8DBQFEiP/X6q4f+IV6B/wRAryEAJwPlQ82ytAlnlveo/B/E0Th9VvDCgCdGkcI |
| 34 |
fHptMLDBVNbDg3AxyVAZ4yQ= |
| 35 |
=9zwc |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-amd64@g.o mailing list |
Archives