;;; anything whose name matches a magic character pattern is
;;; uninterned.
;;;
-;;; FIXME: should also go through globaldb (and perhaps other tables)
-;;; blowing away associated entries
+;;; FIXME: Are there other tables that need to have entries removed?
+;;; What about symbols of the form DEF!FOO?
(defun !unintern-init-only-stuff ()
(do ((any-changes? nil nil))
(nil)
(string= name "*!" :end1 2 :end2 2)))
(/show0 "uninterning cold-init-only symbol..")
(/primitive-print name)
+ ;; FIXME: Is this (FIRST (LAST *INFO-ENVIRONMENT*)) really
+ ;; meant to be an idiom to use? Is there a more obvious
+ ;; name for this? [e.g. (GLOBAL-ENVIRONMENT)?]
+ (do-info ((first (last *info-environment*))
+ :name entry :class class :type type)
+ (when (eq entry symbol)
+ (clear-info class type entry)))
(unintern symbol package)
(setf any-changes? t)))))
(unless any-changes?
\f
;;;; putting ourselves out of our misery when things become too much to bear
-(declaim (ftype (function (simple-string) nil) critically-unreachable))
+(declaim (ftype (function (simple-string) nil) !cold-lose))
(defun !cold-lose (msg)
(%primitive print msg)
(%primitive print "too early in cold init to recover from errors")
;; !UNIX-COLD-INIT. And *TYPE-SYSTEM-INITIALIZED* could be changed to
;; *TYPE-SYSTEM-INITIALIZED-WHEN-BOUND* so that it doesn't need to
;; be explicitly set in order to be meaningful.
- (setf *gc-notify-stream* nil
- *before-gc-hooks* nil
+ (setf *before-gc-hooks* nil
*after-gc-hooks* nil
- *already-maybe-gcing* t
- *gc-inhibit* t
+ *gc-inhibit* 1
*need-to-collect-garbage* nil
sb!unix::*interrupts-enabled* t
sb!unix::*interrupt-pending* nil
;; this to be initialized, so we initialize it right away.
(show-and-call !random-cold-init)
+ (show-and-call !early-package-cold-init)
(show-and-call !package-cold-init)
-
+
;; All sorts of things need INFO and/or (SETF INFO).
(/show0 "about to SHOW-AND-CALL !GLOBALDB-COLD-INIT")
(show-and-call !globaldb-cold-init)
;; This needs to be done early, but needs to be after INFO is
;; initialized.
+ (show-and-call !function-names-cold-init)
(show-and-call !fdefn-cold-init)
;; Various toplevel forms call MAKE-ARRAY, which calls SUBTYPEP, so
(show-and-call !policy-cold-init-or-resanify)
(/show0 "back from !POLICY-COLD-INIT-OR-RESANIFY")
+ (show-and-call !early-proclaim-cold-init)
+
;; KLUDGE: Why are fixups mixed up with toplevel forms? Couldn't
;; fixups be done separately? Wouldn't that be clearer and better?
;; -- WHN 19991204
;; DEFTYPEs are.
(setf *type-system-initialized* t)
+ ;; now that the type system is definitely initialized, fixup UNKNOWN
+ ;; types that have crept in.
+ (show-and-call !fixup-type-cold-init)
+ ;; run the PROCLAIMs.
+ (show-and-call !late-proclaim-cold-init)
+
(show-and-call os-cold-init-or-reinit)
(show-and-call stream-cold-init-or-reset)
(show-and-call !loader-cold-init)
+ (show-and-call !foreign-cold-init)
(show-and-call signal-cold-init-or-reinit)
+ (/show0 "enabling internal errors")
(setf (sb!alien:extern-alien "internal_errors_enabled" boolean) t)
;; FIXME: This list of modes should be defined in one place and
;; explicitly shared between here and REINIT.
- ;; Why was this marked #!+alpha? CMUCL does it here on all architectures
- (set-floating-point-modes :traps '(:overflow :invalid :divide-by-zero))
+ ;; FIXME: For some unknown reason, NetBSD/x86 won't run with the
+ ;; :invalid trap enabled. That should be fixed, but not today...
+ ;; PEM -- April 5, 2004
+ (set-floating-point-modes
+ :traps '(:overflow #!-netbsd :invalid :divide-by-zero))
(show-and-call !class-finalize)
(setf *cold-init-complete-p* t)
;; The system is finally ready for GC.
- (setf *already-maybe-gcing* nil)
(/show0 "enabling GC")
(gc-on)
(/show0 "doing first GC")
(unix-code 0 unix-code-p)
(unix-status unix-code))
#!+sb-doc
- "Terminate the current Lisp. Things are cleaned up (with UNWIND-PROTECT
- and so forth) unless RECKLESSLY-P is non-NIL. On UNIX-like systems,
- UNIX-STATUS is used as the status code."
+ "Terminate the current Lisp. Things are cleaned up (with
+UNWIND-PROTECT and so forth) unless RECKLESSLY-P is non-NIL. On
+UNIX-like systems, UNIX-STATUS is used as the status code."
(declare (type (signed-byte 32) unix-status unix-code))
(/show0 "entering QUIT")
;; FIXME: UNIX-CODE was deprecated in sbcl-0.6.8, after having been
(os-cold-init-or-reinit)
(stream-reinit)
(signal-cold-init-or-reinit)
- (gc-reinit)
(setf (sb!alien:extern-alien "internal_errors_enabled" boolean) t)
;; PRINT seems not to like x86 NPX denormal floats like
;; LEAST-NEGATIVE-SINGLE-FLOAT, so the :UNDERFLOW exceptions are
;; disabled by default. Joe User can explicitly enable them if
;; desired.
- (set-floating-point-modes :traps '(:overflow :invalid :divide-by-zero))
-
- ;; Clear pseudo atomic in case this core wasn't compiled with
- ;; support.
;;
- ;; FIXME: In SBCL our cores are always compiled with support. So
- ;; we don't need to do this, do we? At least not for this
- ;; reason.. (Perhaps we should do it anyway in case someone
- ;; manages to save an image from within a pseudo-atomic-atomic
- ;; operation?)
- #!+x86 (setf *pseudo-atomic-atomic* 0))
- (gc-on)))
+ ;; see also comment at the previous SET-FLOATING-POINT-MODES
+ ;; call site.
+ (set-floating-point-modes
+ :traps '(:overflow #!-netbsd :invalid :divide-by-zero))
+ (sb!thread::maybe-install-futex-functions)))
+ (foreign-reinit)
+ (gc-reinit)
+ (mapc #'funcall *init-hooks*))
\f
;;;; some support for any hapless wretches who end up debugging cold
;;;; init code
projects / sbcl.git / blobdiff