Fall through #2

Bug #2058291 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 -120338 -2052) b))
  (case b
    ((8) (case a ((-14459) 0) ((-7184) a) ((14360 1853) b) (t b)))
    ((-3 -2 4) 0)
    ((7 6) 0)
    (t 0)))

==>

Fall through
This is probably a bug in SBCL itself. (Alternatively, SBCL
might have been corrupted by bad user code, e.g. by an undefined
Lisp operation like (FMAKUNBOUND 'COMPILE), or by stray pointers
from alien code or from unsafe Lisp code; or there might be a
bug in the OS or hardware that SBCL is running on.) If it seems
to be a bug in SBCL itself, the maintainers would like to know
about it. Bug reports are welcome on the SBCL mailing lists,
which you can find at <http://sbcl.sourceforge.net/>.
   [Condition of type SB-INT:BUG]

Restarts:
 0: [RETRY] Retry SLIME REPL evaluation request.
 1: [*ABORT] Return to SLIME's top level.
 2: [ABORT] abort thread (#<THREAD tid=5898 "repl-thread" RUNNING {1000EF8003}>)

Backtrace:
  0: (SB-INT:BUG "Fall through")
  1: (SB-C::PREPARE-JUMP-TABLE-TARGETS #<SB-C::LVAR 1 {1006BE2063}> ((0 . #<SB-C::CBLOCK 5 :START c2 {1006C2D8B3}>) (1 . #<SB-C::CBLOCK 4 :START c3 {1006C2E423}>)))
  2: (SB-C::IR2-CONVERT-JUMP-TABLE #<SB-C:JUMP-TABLE :INDEX #<SB-C::LVAR 1 {1006BE2063}> :TARGETS ((0 . #<SB-C::CBLOCK 5 :START c2 {1006C2D8B3}>) (1 . #<SB-C::CBLOCK 4 :START c3 {1006C2E423}>)) {1006BE20B3..
  3: (SB-C::IR2-CONVERT-BLOCK #<SB-C::CBLOCK 8 :START c4 {1006C20B73}>)
  4: (SB-C:IR2-CONVERT #<SB-C:COMPONENT :NAME "<unknown>" {1006BE6423}>)
  5: (SB-C::%COMPILE-COMPONENT #<SB-C:COMPONENT :NAME "<unknown>" {1006BE6423}>)
  6: (SB-C::COMPILE-COMPONENT #<SB-C:COMPONENT :NAME "<unknown>" {1006BE6423}>)
  7: (SB-C::%COMPILE (LAMBDA (A B) (DECLARE (TYPE # B)) (CASE B (# #) (# 0) (# 0) (T 0))) NIL NIL)
 [...]

x86-64, "2.4.2.200-8a4a8dd68"

Stas Boukarev (stassats)
Changed in sbcl:
status: New → 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.