From: Daniel B. <da...@us...> - 2003-03-26 01:04:45
|
Update of /cvsroot/sbcl/sbcl In directory sc8-pr-cvs1:/tmp/cvs-serv14318 Modified Files: base-target-features.lisp-expr package-data-list.lisp-expr version.lisp-expr Log Message: 0.pre8.10 Add some files needed by the soon-to-be-merged thread support Some non-invasive (supposed not to break unithread builds) changes to existing files ... add SB-THREAD package ... fs-segment-prefix "instruction" definition ... some documentation (OK, so it will break McCLIM. That's easily fixable, though) Index: base-target-features.lisp-expr =================================================================== RCS file: /cvsroot/sbcl/sbcl/base-target-features.lisp-expr,v retrieving revision 1.23 retrieving revision 1.24 diff -u -d -r1.23 -r1.24 --- base-target-features.lisp-expr 15 Sep 2002 14:20:23 -0000 1.23 +++ base-target-features.lisp-expr 26 Mar 2003 01:04:41 -0000 1.24 @@ -152,21 +152,14 @@ ; :high-security ; :high-security-support - ;; multiprocessing support + ;; low-level thread primitives support ;; - ;; This is not maintained or tested in current SBCL. I haven't gone out - ;; of my way to break it, but since it's derived from an old version of - ;; CMU CL where multiprocessing was pretty shaky, it's likely to be very - ;; flaky now. - ;; :MP enables multiprocessing - ;; :MP-I486 is used, only within the multiprocessing code, to control - ;; what seems to control processor-version-specific code. It's - ;; probably for 486 or later, i.e. could be set as long as - ;; you know you're not running on a 386, but it doesn't seem - ;; to be documented anywhere, so that's just a guess. - ; :mp - ; :mp-i486 - + ;; As of SBCL 0.8, this is only supposed to work in x86 Linux, on which + ;; system it's implemented using clone(2) and the %fs segment register. + ;; Note that no consistent effort to audit the SBCL library code for + ;; thread safety has been performed, so caveat executor + ; :sb-thread + ;; This affects the definition of a lot of things in bignum.lisp. It ;; doesn't seem to be documented anywhere what systems it might apply ;; to. It doesn't seem to be needed for X86 systems anyway. Index: package-data-list.lisp-expr =================================================================== RCS file: /cvsroot/sbcl/sbcl/package-data-list.lisp-expr,v retrieving revision 1.206 retrieving revision 1.207 diff -u -d -r1.206 -r1.207 --- package-data-list.lisp-expr 24 Mar 2003 18:38:56 -0000 1.206 +++ package-data-list.lisp-expr 26 Mar 2003 01:04:41 -0000 1.207 @@ -1388,6 +1388,16 @@ "%ARRAY-TYPEP" "%SET-SAP-REF-DESCRIPTOR")) #s(sb-cold:package-data + :name "SB!THREAD" + :use ("CL" "SB!ALIEN") + :doc "public (but low-level): native thread support" + :export ("MAKE-THREAD" + "MAKE-LISTENER-THREAD" "DESTROY-THREAD" "WITH-RECURSIVE-LOCK" + "MUTEX" "MAKE-MUTEX" "GET-MUTEX" "RELEASE-MUTEX" "WITH-MUTEX" + "WAITQUEUE" "MAKE-WAITQUEUE" "CONDITION-WAIT" "CONDITION-NOTIFY" + "WITH-RECURSIVE-LOCK" "RELEASE-FOREGROUND" "CURRENT-THREAD-ID")) + + #s(sb-cold:package-data :name "SB!LOOP" :doc "private: implementation details of LOOP" :use ("CL") Index: version.lisp-expr =================================================================== RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v retrieving revision 1.835 retrieving revision 1.836 diff -u -d -r1.835 -r1.836 --- version.lisp-expr 25 Mar 2003 16:30:57 -0000 1.835 +++ version.lisp-expr 26 Mar 2003 01:04:41 -0000 1.836 @@ -18,4 +18,4 @@ ;;; versions, especially for internal versions off the main CVS ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"0.pre8.9" +"0.pre8.10" |