I think my last email crossed your reply - so apolgies for restating:
expand_builtin_nonlocal_goto is fine. This perform stack restore,
extracts frame pointer value and does jump.
reciever is fine - this jump destination does restore of frame pointer.
The problem I have is with frame pointer value that is saved in by
"setup" prior to all this
For goto is does not use expand_builtin_setjmp_setup - (pathetically) I
can't find what it is using.
Andy
-----Original Message-----
From: Ian Lance Taylor <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: gcc@gcc.gnu.org
Sent: Thu, 22 May 2008 2:26 pm
Subject: Re: Where is setup for "goto" in nested function created?
[EMAIL PROTECTED] writes:
However, for a normal goto used inside a nested function, a
different part of gcc creates the code to store frame pointer (not
expand_builtin_setjmp_setup). I can't find this code.
I think you are looking for expand_builtin_nonlocal_goto in
builtins.c.
Ian
