On Nov 15, 2013, at 4:32 AM, Eric Botcazou wrote:
>> Either you need to document all the semantics so as to make clear to users
>> exactly when they can use these functions safely, or you need to state
>> that there are undocumented restrictions that may change from GCC version
>> to GCC version a
> Are there any other restrictions? Do they, for example, guarantee to
> restore all call-saved registers to their values at the time of the
> __builtin_longjmp call, including those for which libc's setjmp and
> longjmp need to test for existence at runtime (but they may have been used
> in an in
On Sun, 10 Nov 2013, H.J. Lu wrote:
> +@code{__builtin_setjmp} and @code{__builtin_longjmp} may not be used
> +in the same function with the same @code{setjmp} buffer.
Are there any other restrictions? Do they, for example, guarantee to
restore all call-saved registers to their values at the ti
On Nov 10, 2013, at 8:28 AM, H.J. Lu wrote:
> This patch documents __builtin_setjmp and __builtin_longjmp. OK to
> install?
I like it. I think these two should be documented.
Hi,
This patch documents __builtin_setjmp and __builtin_longjmp. OK to
install?
Thanks.
H.J.
---
2013-11-10 H.J. Lu
PR other/59039
* doc/extend.texi: Document __builtin_setjmp and
__builtin_longjmp.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 0d7281
