Be more systematic about _setjmp vs setjmp.
authorPaul Eggert <eggert@cs.ucla.edu>
Tue, 4 Sep 2012 06:34:19 +0000 (23:34 -0700)
committerPaul Eggert <eggert@cs.ucla.edu>
Tue, 4 Sep 2012 06:34:19 +0000 (23:34 -0700)
commitaf26b72c1187a93cdacc6abb6561f3c331346cef
tree12dd2afed044c50078a831bf3aaaa981d79586b8
parent7b6c362efe6e32b6a3a68f6f827c9cc558a2fcf0
Be more systematic about _setjmp vs setjmp.

* alloc.c (test_setjmp, mark_stack):
* image.c (PNG_LONGJMP) [PNG_LIBPNG_VER < 10500]:
(PNG_JMPBUF) [! (PNG_LIBPNG_VER < 10500)]:
(png_load, my_error_exit, jpeg_load):
* process.c (send_process_trap, send_process):
Uniformly prefer _setjmp and _longjmp to setjmp and longjmp.
The underscored versions are up to 30x faster on some hosts.
Formerly, the code used setjmp+longjmp sometimes and
_setjmp+_longjmp at other times, with no particular reason to
prefer setjmp+longjmp.
src/ChangeLog
src/alloc.c
src/image.c
src/process.c