(:vop-var vop)
(:save-p :compute-only)
(:generator 1
- (error-call vop nil-array-accessed-error object)))
+ (error-call vop
+ #!+(or x86 x86-64) 'nil-array-accessed-error
+ #!-(or x86 x86-64) nil-array-accessed-error
+ object)))
;;; It shouldn't be possible to fall through to here in normal user
;;; code, as the system is smart enough to deduce that there must be
(:vop-var vop)
(:save-p :compute-only)
(:generator 1
- (error-call vop nil-array-accessed-error object)))
+ (error-call vop
+ #!+(or x86 x86-64) 'nil-array-accessed-error
+ #!-(or x86 x86-64) nil-array-accessed-error
+ object)))
(define-vop (data-vector-ref-with-offset/simple-array-nil)
(:translate data-vector-ref-with-offset)
(:vop-var vop)
(:save-p :compute-only)
(:generator 1
- (error-call vop nil-array-accessed-error object)))
+ (error-call vop
+ #!+(or x86 x86-64) 'nil-array-accessed-error
+ #!-(or x86 x86-64) nil-array-accessed-error
+ object)))
(define-vop (data-vector-set/simple-array-nil)
(:translate data-vector-set)
(:vop-var vop)
(:save-p :compute-only)
(:generator 1
- (error-call vop nil-array-accessed-error object)))
+ (error-call vop
+ #!+(or x86 x86-64) 'nil-array-accessed-error
+ #!-(or x86 x86-64) nil-array-accessed-error
+ object)))
\f
;;; FIXME: There is probably plenty of other array stuff that looks
;;; the same or similar enough to be genericized. Do so, and move it