Re: Bug: nil not of type number in sb-vm::load-number

Stas Boukarev <[email protected]>
Newsgroups gmane.lisp.steel-bank.devel
Message-ID <CAF63=12Y5yMrTK7Xs5Ecb+ySCoRo2R2zjMEdp8Wm8wnn9+U+9w@mail.gmail.com>
Fixed. Thanks.

On Sat, Jan 24, 2026 at 3:10 PM Eric Marsden via Sbcl-devel
<[email protected]> wrote:
>
> Hi,
>
>  From random-integer testing on AMD64.
>
> * (lisp-implementation-version)
> "2.6.0.163-983025932"
> * (defun foo (a b)
>      (declare (type (integer -3 -2) a))
>      (declare (type (integer -8073308298 221847931) b))
>      (dpb (sbit #*1110010011100 (min 12 0)) (byte 30 0)
>           (ash (expt b 2) (min 22 a))))
> debugger invoked on a TYPE-ERROR @B80000ADD6 in thread
> #<THREAD tid=101952 "main thread" RUNNING {1200BE8003}>:
>    The value
>      NIL
>    is not of type
>      NUMBER
>
> Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
>
> restarts (invokable by number or by possibly-abbreviated name):
>    0: [ABORT] Exit debugger, returning to top level.
>
> (SB-KERNEL:TWO-ARG-= NIL 0)
> 0] backtrace
>
> Backtrace for: #<SB-THREAD:THREAD tid=101952 "main thread" RUNNING
> {1200BE8003}>
> 0: (SB-KERNEL:TWO-ARG-= NIL 0)
> 1: (SB-VM::GENERIC-=)
> 2: (SB-VM::LOAD-NUMBER #<unused argument> #<SB-C:TN 'NIL!1 :CONSTANT>
> #<SB-C:TN t2[RSI(u)] :LOAD>)
> 3: ((SB-C::VOP SB-VM::WORD-MOVE) #<SB-C::VOP :INFO SB-VM::WORD-MOVE
> :ARGS #<SB-C:TN-REF :TN #<SB-C:TN 'NIL!1 :CONSTANT> :WRITE-P NIL :VOP
> SB-VM::WORD-MOVE> :RESULTS #<SB-C:TN-REF :TN #<SB-C:TN t3[RSI(u)]
> :NORMAL> :WRITE-P T :VOP SB-VM::WORD-MOVE>>)
> 4: (SB-C::GENERATE-CODE #<SB-C:COMPONENT :NAME "<unknown>" {120291CFB3}>)
>
>
> _______________________________________________
> Sbcl-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sbcl-devel


_______________________________________________
Sbcl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.