ยท Jan Seeger <[EMAIL PROTECTED]>: > I'd think that using -march overrides -mtune. You cannot at the same time tune > for two architectures.
Hm, what's an "architecture"? From my understanding, I'd need crossdev if I'd try to compile for, lets say, PA-RISC on a x86 system. But that's not what I'm trying to do - I'm trying to compile for x86 on a x86 system. Indeed, I think that I just have mixed up -march and -mtune (aka. -mcpu). The GCC 3.4.6 docs have it quite clear: ,----[ http://gcc.gnu.org/onlinedocs/gcc-3.3.6/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options ] | -mcpu=cpu-type | [...] | While picking a specific cpu-type will schedule things appropriately | for that particular chip, the compiler will not generate any code that | does not run on the i386 without the -march=cpu-type option being used. `---- That's for -mcpu, which is, in 4.x, a deprecated synonym for -mtune. Well, I'll just give it a try. Alexander Skwar -- Another dream that failed. There's nothing sadder. -- Kirk, "This side of Paradise", stardate 3417.3 -- [EMAIL PROTECTED] mailing list
