From: Nikodemus S. <de...@us...> - 2008-05-15 15:37:56
|
Update of /cvsroot/sbcl/sbcl/doc In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv6409/doc Modified Files: sbcl.1 Log Message: 1.0.16.31: --control-stack-size runtime argument * THREAD_CONTROL_STACK_SIZE becomes DEFAULT_CONTROL_STACK_SIZE. * Align thread spaces using the larger of BACKEND_PAGE_SIZE and CONTROL_STACK_ADJUSTMENT_BYTES. * Take care of aligning both ends of the control stack when setting up the thread struct -- that way pthread_attr_setstack doesn't have to worry about alignment. * Simplify stack setup in on x86oid platforms in call_into_lisp_first_time: instead of having the nasty window where ESP/RSP is right at the end of the stack, use pull out the control stack end right out of the thread struct. * Minimal documentation. Not strictly related to --control-stack-size: * Refactor thread post mortem cleanups to share as much code as possible and reduce conditionalization. The core functions in the new world are plan_thread_post_mortem, schedule_thread_post_mortem, and perform_thread_post_mortem. * Malloc thread attributes, and destroy them before freeing thread stacks. (pthread_attr_setstack seems to say that we are not allowed to free stacks that have attributes referring to them -- hopefully pthread_attr_destroy gives us the licence we need, and since it is not entirely clear we are allowed to destroy the attr before the thread has finished, do it only after pthread_join.) Index: sbcl.1 =================================================================== RCS file: /cvsroot/sbcl/sbcl/doc/sbcl.1,v retrieving revision 1.44 retrieving revision 1.45 diff -u -d -r1.44 -r1.45 --- sbcl.1 13 Mar 2008 11:07:45 -0000 1.44 +++ sbcl.1 15 May 2008 15:37:49 -0000 1.45 @@ -261,6 +261,10 @@ Size of the dynamic space reserved on startup in megabytes. Default value is platform dependent. .TP 3 +.B \-\-control-stack-size <megabytes> +Size of control stack reserved for each thread in megabytes. Default value +is 2. +.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 |