The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael_davidson@pacbell.net (Michael Davidson)
Subject: [pups] V7 setjmp/longjmp
Date: Tue, 31 Dec 2002 08:02:37 -0800	[thread overview]
Message-ID: <3E11BF9D.5010903@pacbell.net> (raw)
In-Reply-To: <200212311307.gBVD7p600218@bsd.korb>

Wolfgang Helbig wrote:

>Michael Davidson distrusted:
>
>>Note that this means that r4, r3 and r2 get restored to the values
>>that they had at the time that the next stack frame was established
>>(ie when the "next" function down was called from the original context)
>>and that these are not necessarily the values that they had at the
>>moment when the original call to setjnp returned. Hence the various
>>caveats about not relying on the value of any register variables
>>after returning via longjmp.
>>
>
>You can trust register variables when setjmp() returns the second time. Then
>the registers are restored to the values they had when the "next" function was 
>called, that is the "values as of the time longjmp() was called" (quoted from
>longjmp(3)'s man page. Thus any variable behaves the same, regardless of its
>storage class.
>
Yes, you are right - V7 restores the register variables to a state which
is consistent with the other auto variables in the function - ie the value
which they had when longjmp was called.

The caveats about not relying on register variables applied to V6.





  reply	other threads:[~2002-12-31 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 11:04 Wolfgang Helbig
2002-12-31 16:02 ` Michael Davidson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-25  5:14 Dennis Ritchie
2003-03-23 12:32 Wolfgang Helbig
2002-12-30 18:51 bwc
2002-12-31  2:23 ` Michael Davidson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E11BF9D.5010903@pacbell.net \
    --to=michael_davidson@pacbell.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).