full call to SB-VM::+-MODFX
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
(lambda (a)
(declare
(optimize (safety 3) (debug 1) (speed 2) (compilation-speed 3)
(sb-
(logandc1
(+
(logxor 1
(the (satisfies eval)
1)
1))
==>
full call to SB-VM::+-MODFX
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://
[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=3701 "repl-thread" RUNNING {1000BB8003}>)
Backtrace:
0: (SB-INT:BUG "full call to ~S" SB-VM::+-MODFX)
1: (SB-C::
2: (SB-C::
3: (SB-C::
4: (SB-C:IR2-CONVERT #<SB-C:COMPONENT :NAME "<unknown>" {10052D5B13}>)
5: (SB-C::
6: (SB-C::
7: (SB-C::%COMPILE (LAMBDA (A) (DECLARE (OPTIMIZE # # # # # ...)) (LOGANDC1 (+ # 1) 1)) NIL NIL)
[...]
x86-64, "2.5.0.
Other inputs showing similar failures:
(lambda (a)
(declare (type (integer 5321934508447773999 689073933387585
(declare
(optimize (safety 2) (speed 2) (compilation-speed 0)
(boole boole-andc1
(boole boole-xor 1
a))
and
(lambda (b c)
(declare (type (integer -23411628 26612848) b))
(declare (type (integer -125191834226420 111863328767438) c))
(declare
(optimize (space 3) (debug 1) (speed 3) (safety 3)
(boole boole-orc2
(/
(boole boole-andc1 (the (satisfies eval) (boole boole-nor 1 b))
-1)
1))
Changed in sbcl: | |
status: | New → Fix Released |