[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: setjmp doc fixes
From: |
Bruno Haible |
Subject: |
Re: setjmp doc fixes |
Date: |
Sat, 7 Jun 2008 13:50:03 +0200 |
User-agent: |
KMail/1.5.4 |
> That sounds good to me. Do you want to make the edit?
Done like this:
2008-06-07 Bruno Haible <address@hidden>
* doc/posix-functions/_setjmp.texi: Explain the use of this function
regardless of POSIX.
* doc/posix-functions/_longjmp.texi: Likewise.
* doc/posix-functions/setjmp.texi: Mention HP-UX as not counting as a
SystemV platform in this case.
--- doc/posix-functions/_longjmp.texi.orig 2008-06-07 13:42:43.000000000
+0200
+++ doc/posix-functions/_longjmp.texi 2008-06-07 13:41:38.000000000 +0200
@@ -15,7 +15,10 @@
@item
This function is missing on some platforms:
Solaris 2.5.1, mingw.
-
address@hidden
-This function is obsolete; use @code{siglongjmp} instead.
@end itemize
+
+Note: A future revision of POSIX later than the 2008/2009 one may drop the
+functions @code{_setjmp} and @code{_longjmp}. Still, in 2008, on all
+systems which have @code{_setjmp}, it is the fastest way to save the
+registers but not the signal mask (up to 30 times faster than @code{setjmp}
+on some systems).
--- doc/posix-functions/_setjmp.texi.orig 2008-06-07 13:42:43.000000000
+0200
+++ doc/posix-functions/_setjmp.texi 2008-06-07 13:41:17.000000000 +0200
@@ -15,7 +15,10 @@
@item
This function is missing on some platforms:
Solaris 2.5.1.
-
address@hidden
-This function is obsolete; use @code{sigsetjmp} instead.
@end itemize
+
+Note: A future revision of POSIX later than the 2008/2009 one may drop the
+functions @code{_setjmp} and @code{_longjmp}. Still, in 2008, on all
+systems which have @code{_setjmp}, it is the fastest way to save the
+registers but not the signal mask (up to 30 times faster than @code{setjmp}
+on some systems).
--- doc/posix-functions/setjmp.texi.orig 2008-06-07 13:42:43.000000000
+0200
+++ doc/posix-functions/setjmp.texi 2008-06-07 13:37:47.000000000 +0200
@@ -16,7 +16,8 @@
POSIX does not specify whether @code{setjmp} saves the signal mask in the
@code{jmp_buf}. It does on BSD platforms, and on glibc platforms when
@code{_BSD_SOURCE} is defined; in this case @code{setjmp} behaves like
address@hidden, and functions @code{_setjmp} and @code{_longjmp} are
-available that don't save or restore the signal mask. On System V platforms,
-and on glibc platforms by default, @code{setjmp} doesn't save the signal mask.
address@hidden(.,1)}, and functions @code{_setjmp} and @code{_longjmp} are
+available that don't save or restore the signal mask. On System V platforms
+(excluding HP-UX), and on glibc platforms by default, @code{setjmp} doesn't
+save the signal mask.
@end itemize