| 1 |
On Sun, Dec 3, 2017 at 2:23 AM, Manuel McLure <manuel@××××××.org> 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 Intel |
| 9 |
> Core i5 which should give a nice speed boost, but of course the Intel chip |
| 10 |
> doesn't understand 3dnow or 3dnowext, so I'll have to do a system rebuild |
| 11 |
> before I switch out the motherboard/processor. It seems pretty obvious that |
| 12 |
> I have to take "3dnow 3dnowext" out of CPU_FLAGS_X86, but what CFLAGS would |
| 13 |
> be recommended for a system that will still run with the AMD processor but |
| 14 |
> won't fall over when I switch to the Intel processor? Once I have the Intel |
| 15 |
> in place I can rebuild with options more suited for that chip, but I want to |
| 16 |
> make sure I don't end up in a catch-22 situation. |
| 17 |
|
| 18 |
I would go with just "-O2 -pipe" for maximum compatibility. Remove the |
| 19 |
-march option altogether, and add it back once the system is running |
| 20 |
on the Intel chip. |
Archives