mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
(As per Daniel Barlow sbcl-devel 2001-05-17, the removal of the mysterious "" special case in UNIX-STAT will probably keep this version from building itself, so I didn't even try. It does, however, at least do "sh run-tests.sh" successfully.) fixed declaration in %EXTRACT-STAT-RESULTS so that the system won't have to interpret the alien reference at runtime on every call to the function I found how to fix the boot/gencgc/purify problem which was leaving initial-function unmapped -- I could copy current_region_free_pointer into boxed_region.free_pointer just before gc_alloc_update_page_pages() in save.c. However, that left me with other flaky GC problems. So I gave up my GC hacking in this version as a bad job, and copied original 0.6.12.7 GC-related files over the modified versions: gencgc.c, save.c, purify.c, gc.lisp, save.lisp made %EXTRACT-STAT-RESULTS inline to suppress an apparent memory corruption bug
19 lines
924 B
Plaintext
19 lines
924 B
Plaintext
;;; This is the master value for LISP-IMPLEMENTATION-VERSION. It's
|
|
;;; separated into its own file here so that it's easy for
|
|
;;; text-munging make-ish or cvs-ish scripts to find and tweak it. For
|
|
;;; the convenience of such scripts, only a trivial subset of Lisp
|
|
;;; reader syntax should be used here: semicolon-delimited comments,
|
|
;;; possible blank lines or other whitespace, and a single
|
|
;;; double-quoted string value alone on its own line.
|
|
;;;
|
|
;;; ANSI says LISP-IMPLEMENTATION-VERSION can be NIL "if no
|
|
;;; appropriate and relevant result can be produced", but as long as
|
|
;;; we control the build, we can always assign an appropriate and
|
|
;;; relevant result, so this must be a string, not NIL.
|
|
;;;
|
|
;;; Conventionally a string like "0.6.6" is used for released
|
|
;;; versions, and a string like "0.6.5.12" is used for versions which
|
|
;;; aren't released but correspond only to CVS tags or snapshots.
|
|
|
|
"0.6.12.7.flaky1.1"
|