The value NIL is not of type SB-C:TN-REF

Bug #1966624 reported by Paul F. Dietz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Fix Released
Undecided
Unassigned

Bug Description

(lambda (a b)
  (declare (type (integer -2039473853 66204340851628) a))
  (max 0
       (handler-case
           (values a
                   (catch 'ct2 0)
                   (sbit #*0001000111 (min 9 (max 0 b)))
                   ))))

==>

The value
  NIL
is not of type
  SB-C:TN-REF
   [Condition of type TYPE-ERROR]
[...]
  0: (SB-C::VOP-OPTIMIZE-DATA-VECTOR-REF-WITH-OFFSET/SIMPLE-BIT-VECTOR-C-OPTIMIZER #<SB-C::VOP :INFO SB-VM::DATA-VECTOR-REF-WITH-OFFSET/SIMPLE-BIT-VECTOR :ARGS #<SB-C:TN-REF :TN #<SB-C:TN '#*0001000111!1[C..
  1: (SB-C::RUN-VOP-OPTIMIZERS #<SB-C:COMPONENT :NAME (SB-C::ESCAPE-FUN #:EXIT-BLOCK-5) {10165BBAC3}>)
  2: (SB-C::IR2-OPTIMIZE #<SB-C:COMPONENT :NAME (SB-C::ESCAPE-FUN #:EXIT-BLOCK-5) {10165BBAC3}>)
[...]

Stas Boukarev (stassats)
Changed in sbcl:
assignee: nobody → Stas Boukarev (stassats)
status: New → Confirmed
Revision history for this message
Christophe Rhodes (csr21-cantab) wrote :

Thanks. This is not a regression from sbcl-2.2.2 so a post-2.2.3 fix is fine.

Revision history for this message
Stas Boukarev (stassats) wrote :

Right, although a check for NIL would've been fine during the freeze, the proper solution is more complicated.

Revision history for this message
Stas Boukarev (stassats) wrote :
Stas Boukarev (stassats)
Changed in sbcl:
status: Confirmed → Fix Committed
assignee: Stas Boukarev (stassats) → nobody
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.