(declare (optimize (safety 0) (speed 3)))
(sb!vm::locked-symbol-global-value-add ',symbol-name ,delta)))
-;;; When >0, inhibits garbage collection.
-(declaim (type index *gc-inhibit*))
(defvar *gc-inhibit*) ; initialized in cold init
+;;; When the dynamic usage increases beyond this amount, the system
+;;; notes that a garbage collection needs to occur by setting
+;;; *GC-PENDING* to T. It starts out as NIL meaning nobody has figured
+;;; out what it should be yet.
+(defvar *gc-pending* nil)
+
+#!+sb-thread
+(defvar *stop-for-gc-pending* nil)
+
(defmacro without-gcing (&body body)
#!+sb-doc
- "Executes the forms in the body without doing a garbage collection."
+ "Executes the forms in the body without doing a garbage collection. It
+inhibits both automatically and explicitly triggered collections. Finally,
+upon leaving the BODY if gc is not inhibited it runs the pending gc.
+Similarly, if gc is triggered in another thread then it waits until gc is
+enabled in this thread.
+
+Implies SB-SYS:WITHOUT-INTERRUPTS for BODY, and causes any nested
+SB-SYS:WITH-INTERRUPTS to signal a warning during execution of the BODY.
+
+Should be used with great care, and not at all in multithreaded application
+code: Any locks that are ever acquired while GC is inhibited need to be always
+held with GC inhibited to prevent deadlocks: if T1 holds the lock and is
+stopped for GC while T2 is waiting for the lock inside WITHOUT-GCING the
+system will be deadlocked. Since SBCL does not currently document its internal
+locks, application code can never be certain that this invariant is
+maintained."
`(unwind-protect
- (progn
- (atomic-incf/symbol *gc-inhibit*)
- ,@body)
- (atomic-incf/symbol *gc-inhibit* -1)
- (when (and *need-to-collect-garbage* (zerop *gc-inhibit*))
- (sub-gc))))
+ (without-interrupts
+ (let ((*gc-inhibit* t))
+ ,@body))
+ ;; the test is racy, but it can err only on the overeager side
+ (sb!kernel::maybe-handle-pending-gc)))
\f
;;; EOF-OR-LOSE is a useful macro that handles EOF.
`(,function stream ,@args)))))
`(funcall (,slot stream) stream ,@args))))
-(defmacro with-out-stream (stream (slot &rest args) &optional stream-dispatch)
- `(let ((stream (out-synonym-of ,stream)))
+(defmacro with-out-stream/no-synonym (stream (slot &rest args) &optional stream-dispatch)
+ `(let ((stream ,stream))
,(if stream-dispatch
`(if (ansi-stream-p stream)
(funcall (,slot stream) stream ,@args)
`(,(destructuring-bind (function &rest args) stream-dispatch
`(,function stream ,@args)))))
`(funcall (,slot stream) stream ,@args))))
+
+(defmacro with-out-stream (stream (slot &rest args) &optional stream-dispatch)
+ `(with-out-stream/no-synonym (out-synonym-of ,stream)
+ (,slot ,@args) ,stream-dispatch))
+
\f
;;;; These are hacks to make the reader win.
;;; This macro sets up some local vars for use by the
;;; FAST-READ-CHAR macro within the enclosed lexical scope. The stream
;;; is assumed to be a ANSI-STREAM.
+;;;
+;;; KLUDGE: Some functions (e.g. ANSI-STREAM-READ-LINE) use these variables
+;;; directly, instead of indirecting through FAST-READ-CHAR.
(defmacro prepare-for-fast-read-char (stream &body forms)
`(let* ((%frc-stream% ,stream)
(%frc-method% (ansi-stream-in %frc-stream%))
`(setf (ansi-stream-in-index %frc-stream%) %frc-index%))
;;; a macro with the same calling convention as READ-CHAR, to be used
-;;; within the scope of a PREPARE-FOR-FAST-READ-CHAR
+;;; within the scope of a PREPARE-FOR-FAST-READ-CHAR.
(defmacro fast-read-char (&optional (eof-error-p t) (eof-value ()))
`(cond
((not %frc-buffer%)