I've checked in this patch to address one of the long-standing
documentation bugs reported in PR 1078.
-Sandra
2016-01-01 Sandra Loosemore <san...@codesourcery.com>
PR 1078
gcc/
* extend.texi (Common Function Attributes) <no_stack_limit>: New.
* invoke.texi (Code Gen Options) <-fno-stack-limit>: Add pointer
to corresponding attribute.
Index: extend.texi
===================================================================
--- extend.texi (revision 232030)
+++ extend.texi (working copy)
@@ -2877,6 +2877,12 @@ prologue which decides whether to split
@code{no_split_stack} attribute do not have that prologue, and thus
may run with only a small amount of stack space available.
+@item no_stack_limit
+@cindex @code{no_stack_limit} function attribute
+This attribute locally overrides the @option{-fstack-limit-register}
+and @option{-fstack-limit-symbol} command-line options; it has the effect
+of disabling stack limit checking in the function it applies to.
+
@item noclone
@cindex @code{noclone} function attribute
This function attribute prevents a function from being considered for
Index: invoke.texi
===================================================================
--- invoke.texi (revision 232030)
+++ invoke.texi (working copy)
@@ -24631,6 +24631,9 @@ and grows downwards, you can use the fla
@option{-Wl,--defsym,__stack_limit=0x7ffe0000} to enforce a stack limit
of 128KB@. Note that this may only work with the GNU linker.
+You can locally override stack limit checking by using the
+@code{no_stack_limit} function attribute (@pxref{Function Attributes}).
+
@item -fsplit-stack
@opindex fsplit-stack
Generate code to automatically split the stack before it overflows.
