This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How should -ffixed-@var{reg} global registers be identified for setjump coding?
- From: Ramana Radhakrishnan <ramana dot r at gmail dot com>
- To: Paul Schlie <schlie at comcast dot net>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sun, 30 Jan 2005 10:35:05 +0530
- Subject: Re: How should -ffixed-@var{reg} global registers be identified for setjump coding?
- References: <BE21D291.8D26%schlie@comcast.net>
- Reply-to: Ramana Radhakrishnan <ramana dot r at gmail dot com>
Hi,
This was raised in the mailing list earlier this month .
http://gcc.gnu.org/ml/gcc/2005-01/msg00902.html contains the reply .
Its not possible for ffixed-reg to be used with setjmp / longjmp with
the features that you want right now AFAIK. The reply to that thread
deals with a case that you might like to see.
HTH
cheers
Ramana
On Sat, 29 Jan 2005 23:53:53 -0500, Paul Schlie <schlie@comcast.net> wrote:
> Although it may be staring me in the face, what's is the proper method
> to identify compile-time -ffixed-@var{reg} declared global-registers
> so that they may be properly excluded from being saved/restored by a
> set/longjump routine implementation?
>
> Any insight would be appreciated, thanks, -paul-
>
>
--
Ramana Radhakrishnan