Gentoo Archives: gentoo-user

From: Walter Dnes <waltdnes@××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] CFLAGS for both AMD64 and Intel?
Date: Sun, 03 Dec 2017 08:09:03
Message-Id: 20171203080852.GB30078@waltdnes.org
In Reply to: [gentoo-user] CFLAGS for both AMD64 and Intel? by Manuel McLure
1 On Sat, Dec 02, 2017 at 11:23:10PM -0800, Manuel McLure wrote
2 > Here's the situation. I have a system that's been running for many years
3 > with an Athlon 5050e processor. The system is built with
4 >
5 > CFLAGS="-march=k8-sse3 -O2 -pipe -msse3"
6 > CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext sse sse2 sse3"
7 >
8 > I have the possibility of upgrading the system to a first-generation
9 > Intel Core i5 which should give a nice speed boost, but of course the
10 > Intel chip doesn't understand 3dnow or 3dnowext, so I'll have to do
11 > a system rebuild before I switch out the motherboard/processor. It
12 > seems pretty obvious that I have to take "3dnow 3dnowext" out of
13 > CPU_FLAGS_X86, but what CFLAGS would be recommended for a system
14 > that will still run with the AMD processor but won't fall over when
15 > I switch to the Intel processor? Once I have the Intel in place I
16 > can rebuild with options more suited for that chip, but I want to
17 > make sure I don't end up in a catch-22 situation.
18
19 https://gcc.gnu.org/onlinedocs/gcc-6.4.0/gcc/x86-Options.html#x86-Options
20 lists what instruction sets gcc expects for any "-march=<whatever>"
21
22 I would suggest rebuilding with...
23
24 CFLAGS="-march=nocona -O2 -pipe"
25 CPU_FLAGS_X86="mmx sse sse2 sse3"
26
27 nocona was the first Intel cpu to support AMD64 instructions, and it's
28 the newest Intel that does not exceed your AMD. The next Intel cpu, the
29 "core2" supports ssse3 which your AMD does not (count the "s"'s... very
30 carefully; sse3 != ssse3).
31
32 --
33 Walter Dnes <waltdnes@××××××××.org>
34 I don't run "desktop environments"; I run useful applications

Replies

Subject Author
Re: [gentoo-user] CFLAGS for both AMD64 and Intel? Manuel McLure <manuel@××××××.org>