| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
maxim wexler wrote: |
| 5 |
> |
| 6 |
> For an 900A w/intel Atom? |
| 7 |
> |
| 8 |
> This is what I get: |
| 9 |
> |
| 10 |
> Warning: Your compiler supports the -march=native option which you |
| 11 |
> may prefer |
| 12 |
|
| 13 |
If you use this, then you 1) must be using >=sys-devel/gcc-4.2, and 2) |
| 14 |
will always have the "best" optimization for your machine, so far as the |
| 15 |
version of gcc you are using understands. |
| 16 |
|
| 17 |
> Warning: Newer versions of GCC better support your CPU with -march=atom |
| 18 |
|
| 19 |
In order to use this, you will need gcc-4.5, which hasn't been released yet. |
| 20 |
|
| 21 |
> -march=core2 -mtune=pentium -mfpmath=sse. |
| 22 |
|
| 23 |
This is the recommendation that the script actually made - it suggests |
| 24 |
to use all of these. |
| 25 |
|
| 26 |
> Now I'm confused. It says *my* compiler supports -march=native. Then |
| 27 |
> it says "Newer versions". Isn't v4.3.2 new? It was from a new pkg about |
| 28 |
> a month ago. Is it giving me a choice here? Can I really declare two |
| 29 |
> -march variables? What about mtune and mfpath, are they meant to be |
| 30 |
> "instead of" or "in addition to"? What goes in the kernel config? What |
| 31 |
> in /etc/paludis/bashrc? |
| 32 |
|
| 33 |
The newest version of gcc out right now is 4.4.0 (currently in |
| 34 |
package.mask). I would suggest setting CFLAGS="-O2 -march=native -pipe" |
| 35 |
and CXXFLAGS="-O2 -march=native -pipe" in /etc/paludis/bashrc (assuming |
| 36 |
that that is the proper location for those variables). |
| 37 |
|
| 38 |
- -- |
| 39 |
ABCD |
| 40 |
-----BEGIN PGP SIGNATURE----- |
| 41 |
Version: GnuPG v2.0.11 (GNU/Linux) |
| 42 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 43 |
|
| 44 |
iEYEARECAAYFAkoXGvUACgkQOypDUo0oQOoDGgCfQdRS+hQtTVKIITl2UvExt5NH |
| 45 |
6g4AoJvL7fC2+Gr2KlYIS3WqMnyeJ9qE |
| 46 |
=1r28 |
| 47 |
-----END PGP SIGNATURE----- |
Archives