* Re: [gentoo-user] CFLAGS for both AMD64 and Intel?
@ 2017-12-03 8:08 99% ` Walter Dnes
0 siblings, 0 replies; 1+ results
From: Walter Dnes @ 2017-12-03 8:08 UTC (permalink / raw
To: gentoo-user
On Sat, Dec 02, 2017 at 11:23:10PM -0800, Manuel McLure wrote
> Here's the situation. I have a system that's been running for many years
> with an Athlon 5050e processor. The system is built with
>
> CFLAGS="-march=k8-sse3 -O2 -pipe -msse3"
> CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext sse sse2 sse3"
>
> I have the possibility of upgrading the system to a first-generation
> Intel Core i5 which should give a nice speed boost, but of course the
> Intel chip doesn't understand 3dnow or 3dnowext, so I'll have to do
> a system rebuild before I switch out the motherboard/processor. It
> seems pretty obvious that I have to take "3dnow 3dnowext" out of
> CPU_FLAGS_X86, but what CFLAGS would be recommended for a system
> that will still run with the AMD processor but won't fall over when
> I switch to the Intel processor? Once I have the Intel in place I
> can rebuild with options more suited for that chip, but I want to
> make sure I don't end up in a catch-22 situation.
https://gcc.gnu.org/onlinedocs/gcc-6.4.0/gcc/x86-Options.html#x86-Options
lists what instruction sets gcc expects for any "-march=<whatever>"
I would suggest rebuilding with...
CFLAGS="-march=nocona -O2 -pipe"
CPU_FLAGS_X86="mmx sse sse2 sse3"
nocona was the first Intel cpu to support AMD64 instructions, and it's
the newest Intel that does not exceed your AMD. The next Intel cpu, the
"core2" supports ssse3 which your AMD does not (count the "s"'s... very
carefully; sse3 != ssse3).
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2017-12-03 7:23 [gentoo-user] CFLAGS for both AMD64 and Intel? Manuel McLure
2017-12-03 8:08 99% ` Walter Dnes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox