On Sat, Jul 21, 2012 at 10:27 AM, Mike Stump <mikest...@comcast.net> wrote: > On Jul 21, 2012, at 9:12 AM, Iain Sandoe wrote: >> At present, if a G5 or 970 processor is selected (-mcpu=), we can (and do) >> generate 64 bit register usage for m32 code. This appears to be a >> long-standing bug. > > Hum, do you have an example of something that fails? I ask, cause I think > the if you say that you have a 64-bit processor, then, generating code for a > 64-bit processor isn't necessarily wrong. If you say you have a 64-bit > processor, then you likely have an OS that runs on that processor, and that > OS I'm thinking will save and restore the full 64-bit registers. If not, do > you have a pointer to documentation that says this won't work?
In fact OS_MISSING_POWERPC64 was added because GNU/Linux does not have support but Darwin has the support in the OS. The whole point of -mpu=G5 means generate G5 code which includes generating PowerPC64 code. This was added explicitly to speed up code like crafty in SPEC. Do you have any data that says it should be disabled? If you don't want to generate powerpc64 code then use -mno-powerpc64. Thanks, Andrew Pinski
