mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
073fc2ae57
* Differ UVL and DX LVARs in IR1 component printout. * %LISTIFY-REST-ARGS treats DX in the same way as LIST. * Replace (SETF (FUN-INFO-STACK-ALLOCATE-RESULT ...)) with DEFOPTIMIZER. * DEFOPTIMIZER interns FUN-INFO-* into SB[!-]C. * Physenv analysis does not insert %DYNAMIC-EXTENT-END when not needed. * Pull Christophe[?] out of hell: replace *DYNAMIC-EXTENT* hack with MAYBE-PSEUDO-ATOMIC macro. * Changed representation of LVAR-DYNAMIC-EXTENT: now it is a CLEANUP or NULL. * LET-variable substitution does not break stack allocation. * DX propagation in SUBSTITUTE-LVAR-USES.
21 lines
1.1 KiB
Plaintext
21 lines
1.1 KiB
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 simple 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", with three numeric fields,
|
|
;;; is used for released versions, and a string like "0.6.5.xyzzy",
|
|
;;; with something arbitrary in the fourth field, is used for CVS
|
|
;;; checkins which aren't released. (And occasionally for internal
|
|
;;; versions, especially for internal versions off the main CVS
|
|
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
|
|
"0.8.13-dx.2"
|