* frame pointer must be single register?
@ 2011-07-08 17:07 DJ Delorie
2011-07-08 17:10 ` Paul Koning
2011-07-08 17:15 ` Jeff Law
0 siblings, 2 replies; 4+ messages in thread
From: DJ Delorie @ 2011-07-08 17:07 UTC (permalink / raw)
To: gcc
Is there an unwritten rule that the frame pointer must be a single
hard register? I'm working on a port where $fp is a register pair,
and I've seen gcc allocate the second register to other things
(causing all sorts of problems).
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: frame pointer must be single register?
2011-07-08 17:07 frame pointer must be single register? DJ Delorie
@ 2011-07-08 17:10 ` Paul Koning
2011-07-08 17:15 ` Jeff Law
1 sibling, 0 replies; 4+ messages in thread
From: Paul Koning @ 2011-07-08 17:10 UTC (permalink / raw)
To: DJ Delorie; +Cc: gcc
On Jul 8, 2011, at 1:07 PM, DJ Delorie wrote:
>
> Is there an unwritten rule that the frame pointer must be a single
> hard register? I'm working on a port where $fp is a register pair,
> and I've seen gcc allocate the second register to other things
> (causing all sorts of problems).
Would it suffice simply to mark the second register as a reserved register? That should take it away from the allocator, right?
paul
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: frame pointer must be single register?
2011-07-08 17:07 frame pointer must be single register? DJ Delorie
2011-07-08 17:10 ` Paul Koning
@ 2011-07-08 17:15 ` Jeff Law
2011-07-08 18:02 ` Georg-Johann Lay
1 sibling, 1 reply; 4+ messages in thread
From: Jeff Law @ 2011-07-08 17:15 UTC (permalink / raw)
To: DJ Delorie; +Cc: gcc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/08/11 11:07, DJ Delorie wrote:
> Is there an unwritten rule that the frame pointer must be a single
> hard register? I'm working on a port where $fp is a register pair,
> and I've seen gcc allocate the second register to other things
> (causing all sorts of problems).
It's certainly caused problems (some of which I believe have been fixed
within the last year or so)... I think there's a port (AVR?) that may
have similar characteristics.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOFzsGAAoJEBRtltQi2kC7YSkH/20Fa0BrXzM4sfRmwcW53wPe
dCR+s9Th6QvvNuBnV3i+J3p6tq+5pefr4VxtpZaQsJ8cXjxbxJpgtFB9wKH2Avn9
5KIlTufjzXD5wVsXOFxyE2VGgmJn5JLyd4vGPYaUShw4VYFN7XyqJ8N4Gvp+Out2
kfdYD3R5T2Slm2ZKdWMoIFkCE2hb1D9kurWWL6kKE4uSI/5KHJxGDLD2iNrKOq8Y
MiMySxsRy95oxx3Y5c8SyA6Xi02HVTwdCn/orycO/JN569ngRz3IX6JL/zT+GKTA
fYf0KTeeN9FuPItixvdq/MCenvLSUdPJcjxksvK+X8c+hv5v/5gOUZONcrAU0SA=
=rLHD
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: frame pointer must be single register?
2011-07-08 17:15 ` Jeff Law
@ 2011-07-08 18:02 ` Georg-Johann Lay
0 siblings, 0 replies; 4+ messages in thread
From: Georg-Johann Lay @ 2011-07-08 18:02 UTC (permalink / raw)
To: Jeff Law; +Cc: DJ Delorie, gcc
Jeff Law wrote:
> On 07/08/11 11:07, DJ Delorie wrote:
>> Is there an unwritten rule that the frame pointer must be a single
>> hard register? I'm working on a port where $fp is a register pair,
>> and I've seen gcc allocate the second register to other things
>> (causing all sorts of problems).
> It's certainly caused problems (some of which I believe have been fixed
> within the last year or so)... I think there's a port (AVR?) that may
> have similar characteristics.
>
> jeff
Yes, and fixing the second part appears not to be the right approach.
I just committed a patch to fix PR46779, PR45291.
Johann
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-07-08 18:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-07-08 17:07 frame pointer must be single register? DJ Delorie
2011-07-08 17:10 ` Paul Koning
2011-07-08 17:15 ` Jeff Law
2011-07-08 18:02 ` Georg-Johann Lay
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).