0.8.9.45:

[sbcl.git] / src / compiler / early-c.lisp

diff --git a/src/compiler/early-c.lisp b/src/compiler/early-c.lisp
index 1faa6f8..6b793b7 100644 (file)
--- a/src/compiler/early-c.lisp
+++ b/src/compiler/early-c.lisp
@@ -107,7 +107,7 @@
 (defvar *event-info*)
 (defvar *event-note-threshold*)
 (defvar *failure-p*)
-(defvar *fixups*)
+(defvar *fixup-notes*)
 (defvar *in-pack*)
 (defvar *info-environment*)
 (defvar *lexenv*)
@@ -116,6 +116,11 @@
 (defvar *undefined-warnings*)
 (defvar *warnings-p*)
 
+;;; This lock is seized in the compiler, and related areas: the
+;;; compiler is not presently thread-safe
+(defvar *big-compiler-lock*
+  (sb!thread:make-mutex :name "big compiler lock"))
+
 ;;; unique ID for the next object created (to let us track object
 ;;; identity even across GC, useful for understanding weird compiler
 ;;; bugs where something is supposed to be unique but is instead
@@ -174,6 +179,7 @@ convention (names like *FOO*) for special variables" symbol))
 ;;; FIXME: This function seems to have a lot in common with
 ;;; STRINGIFY-FORM, and perhaps there's some way to merge the two
 ;;; functions.
+(declaim (ftype (sfunction (string &rest t) string) debug-namify))
 (defun debug-namify (format-string &rest format-arguments)
   (with-standard-io-syntax
    (let ((*print-readably* nil)