This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, Darwin, ppc] constrain processor usage for m32.
- From: Mike Stump <mikestump at comcast dot net>
- To: Iain Sandoe <iain at codesourcery dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 21 Jul 2012 10:27:36 -0700
- Subject: Re: [Patch, Darwin, ppc] constrain processor usage for m32.
- References: <BF346973-7FFC-4809-8F42-3A3BACBCE2E0@codesourcery.com>
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?