|setjmp/longjmp implementations email@example.com (1994-02-16)|
|Summary of setjmp/longjmp responses firstname.lastname@example.org (1994-02-17)|
|Re: Summary of setjmp/longjmp responses email@example.com (1994-02-18)|
|Re: Summary of setjmp/longjmp responses firstname.lastname@example.org (1994-02-18)|
|Summary of setjmp/longjmp responses email@example.com (1994-02-22)|
|Date:||Tue, 22 Feb 1994 20:00:11 GMT|
> Thanks to those who responded re my setjmp/longjmp questions. ...
> 1. No commonly used benchmarks depend upon setjmp/longjmp performance.
> [If this is so, I'm amazed that setjmp/longjmp work at all! :-). ]
Given that the main loop of every shell I've ever seen includes a
setjmp call, and error situations are handled by longjmp'ing to the
setjmp'ed address, I would say it would become pretty obvious that
setjmp/long jmp wasn't working. It just doesn't have to work FAST.
Note on some systems, longjmp has to do a system call (typically
_sigreturn) in order to allow longjmp's from signal handlers to work
(the _sigreturn would clear out signal state).
Michael Meissner email: firstname.lastname@example.org phone: 617-621-8861
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142
Return to the
Search the comp.compilers archives again.