full call to SB-KERNEL:DATA-VECTOR-REF-WITH-OFFSET

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

Bug Description

(lambda (b c)
  (declare (type (integer -91432273206611093 235098957974705007) b))
  (declare (type (integer 5111121037251818 160356848682624525) c))
  (declare (optimize (space 0)))
  (sbit #*010110001 (gcd 2 (max b c))))

==>

full call to SB-KERNEL:DATA-VECTOR-REF-WITH-OFFSET
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]
[...]
Backtrace:
  0: (SB-INT:BUG "full call to ~S" SB-KERNEL:DATA-VECTOR-REF-WITH-OFFSET)
  1: (SB-C::PONDER-FULL-CALL #<SB-C::COMBINATION :FUN #<SB-C::REF :LEAF #<SB-C::GLOBAL-VAR :%SOURCE-NAME SB-KERNEL:DATA-VECTOR-REF-WITH-OFFSET :TYPE #1=#<SB-KERNEL:FUN-TYPE #> :DEFINED-TYPE #1# :WHERE-FRO..
  2: (SB-C::IR2-CONVERT-FULL-CALL #<SB-C::COMBINATION :FUN #<SB-C::REF :LEAF #<SB-C::GLOBAL-VAR :%SOURCE-NAME SB-KERNEL:DATA-VECTOR-REF-WITH-OFFSET :TYPE #1=#<SB-KERNEL:FUN-TYPE #> :DEFINED-TYPE #1# :WHER..
  3: (SB-C::IR2-CONVERT-BLOCK #<SB-C::CBLOCK 26 :START c2 {1035B82A33}>)
  4: (SB-C:IR2-CONVERT #<SB-C:COMPONENT :NAME (LAMBDA (B C)) {1035B73D03}>)
  5: (SB-C::%COMPILE-COMPONENT #<SB-C:COMPONENT :NAME (LAMBDA (B C)) {1035B73D03}>)
[...]

Stas Boukarev (stassats)
Changed in sbcl:
status: New → Fix Committed
Revision history for this message
Robert Brown (robert-brown) wrote :

The Git commit that introduced this bug is:

6b10858f9d14220966c5d2d8afa7dc1bd0ccdfad
Rationalize the build order and remove some early- files.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers