1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Tue, 15 Apr 2014 14:33:47 -0400, Walter Dnes |
5 |
<mailto:dwnoon@××××××××.com> (waltdnes@××××××××.org) wrote about "Re: |
6 |
[gentoo-user] Questions about CPU settings in kernel and USE" (in |
7 |
<20140415183347.GA16109@××××××××.org>): |
8 |
|
9 |
> On Tue, Apr 15, 2014 at 03:42:31PM +0100, David W Noon wrote |
10 |
> |
11 |
>> If you specify -march=k8 in your CFLAGS, you should get pretty |
12 |
>> decent object code from GCC. |
13 |
> |
14 |
> I've used "-march=native" since it became available, because it's |
15 |
> one less thing to worry about. That's why I didn't ask about |
16 |
> CFLAGS. |
17 |
> |
18 |
> "echo | gcc -### -E - -march=native" spits out a whole bunch of |
19 |
> diagnostic output. In my case, it includes "-march=amdfam10", so |
20 |
> "-march=native" looks better. |
21 |
|
22 |
That's fine. The only thing is that many people use distcc to compile |
23 |
packages for a laptop on a desktop or server, and -march=native |
24 |
usually has different semantics on the server than on the laptop; thus |
25 |
it is better in such a situation to specify the hardware architecture |
26 |
explicitly. |
27 |
|
28 |
If you're not using distcc, no problems should arise. |
29 |
|
30 |
You should also check your CHOST setting to ensure you have |
31 |
x86_64-pc-linux-gnu specified. |
32 |
- -- |
33 |
Regards, Dave [RLU #314465] |
34 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
35 |
dwnoon@××××××××.com |
36 |
(David W Noon) |
37 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v2.0.22 (GNU/Linux) |
40 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
41 |
|
42 |
iEYEARECAAYFAlNNf50ACgkQRQ2Fs59Psv+tbwCgqwppw1+2j9SLQLGhcRVzyQ4G |
43 |
7jgAmwc3DlJjPyf0SrmFnQ1R6CrX/t0X |
44 |
=s2VQ |
45 |
-----END PGP SIGNATURE----- |