mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
Document --tls-limit
This commit is contained in:
parent
b05bc63e94
commit
c90e6cde90
|
|
@ -213,6 +213,10 @@ value is platform dependent.
|
|||
Size of control stack reserved for each thread in megabytes. Default
|
||||
value is 2.
|
||||
|
||||
@item --tls-limit @var{positive integer}
|
||||
Maximum number of thread-local symbols in threaded builds. Default
|
||||
value is 4096.
|
||||
|
||||
@item --noinform
|
||||
Suppress the printing of any banner or other informational message at
|
||||
startup. This makes it easier to write Lisp programs which work
|
||||
|
|
@ -228,7 +232,7 @@ with LDB.
|
|||
|
||||
@item --lose-on-corruption
|
||||
@cindex ldb
|
||||
There are some dangerous low level errors (for instance, control stack
|
||||
There are some dangerous low-level errors (for instance, control stack
|
||||
exhausted, memory fault) that (or whose handlers) can corrupt the
|
||||
image. By default SBCL prints a warning, then tries to continue and
|
||||
handle the error in Lisp, but this will not always work and SBCL may
|
||||
|
|
|
|||
|
|
@ -100,6 +100,11 @@ The last point means that
|
|||
|
||||
prints @code{0} and not @code{1} as of 0.9.6.
|
||||
|
||||
Note, however, that there is a hard limit on the number of distinct
|
||||
symbols that can be bound dynamically in threaded builds (see
|
||||
@code{--tls-index} in @ref{Runtime Options}). Exceeding this limit
|
||||
triggers the low-level error ``Thread local storage exhausted.''
|
||||
|
||||
@node Atomic Operations
|
||||
@comment node-name, next, previous, up
|
||||
@section Atomic Operations
|
||||
|
|
|
|||
|
|
@ -98,6 +98,10 @@ is platform dependent.
|
|||
Size of control stack reserved for each thread in megabytes. Default value
|
||||
is 2.
|
||||
.TP 3
|
||||
.B \-\-tls-limit <positive integer>
|
||||
Maximum number of thread-local symbols in threaded builds. Default
|
||||
value is 4096.
|
||||
.TP 3
|
||||
.B \-\-noinform
|
||||
Suppress the printing of any banner or other informational message at
|
||||
startup. (This makes it easier to write Lisp programs which work
|
||||
|
|
|
|||
Loading…
Reference in a new issue