* PA is not needed with stack allocation.
* Also rename the first argument to MAYBE-PSEUDO-ATOMIC to
NOT-REALLY-P to avoid confusion.
(:results (result :scs (descriptor-reg)))
(:node-var node)
(:generator 50
- (pseudo-atomic
+ (maybe-pseudo-atomic stack-allocate-p
(allocation result (pad-data-block words) node stack-allocate-p)
(inst lea result (make-ea :byte :base result :disp lowtag))
(when type
;;; place and there's no logical single place to attach documentation.
;;; grep (mostly in src/runtime) is your friend
-;;; FIXME: THIS NAME IS BACKWARDS!
-(defmacro maybe-pseudo-atomic (really-p &body body)
- `(if ,really-p
+(defmacro maybe-pseudo-atomic (not-really-p &body body)
+ `(if ,not-really-p
(progn ,@body)
(pseudo-atomic ,@body)))
,@cases)))))
(aver (null type))
(inst call (make-fixup dst :assembly-routine)))
- (pseudo-atomic
+ (maybe-pseudo-atomic stack-allocate-p
(allocation result (pad-data-block words) node stack-allocate-p)
(inst lea result (make-ea :byte :base result :disp lowtag))
(when type
;;; does not matter whether a signal occurs during construction of a
;;; dynamic-extent object, as the half-finished construction of the
;;; object will not cause any difficulty. We can therefore elide
-(defmacro maybe-pseudo-atomic (really-p &body forms)
- `(if ,really-p
+(defmacro maybe-pseudo-atomic (not-really-p &body forms)
+ `(if ,not-really-p
(progn ,@forms)
(pseudo-atomic ,@forms)))
;;; 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".)
-"1.0.16.21"
+"1.0.16.22"