Re: Bug: full call to SB-C::ASH-INTO-WORD-MOD
Stas Boukarev <[email protected]>
| Newsgroups | gmane.lisp.steel-bank.devel |
|---|---|
| Message-ID | <CAF63=10xWTZFufuaOWHy6oJHe7Kp1TKRBQx1PKG-DN5y2CAhtw@mail.gmail.com> |
Fixed. Thanks. On Sun, Dec 7, 2025 at 2:02 PM Eric Marsden via Sbcl-devel <[email protected]> wrote: > > Hi, > > From random-integer testing on AMD64. > > * (lisp-implementation-version) > "2.5.11.45-0b8038d3d" > * (defun foo (a b) > (logbitp 3 > (when a > (ash (loop for i below 0 sum 1) > (dotimes (i 1 -5) b))))) > > ; in: DEFUN FOO > ; (SB-INT:NAMED-LAMBDA FOO > ; (A B) > ; (BLOCK FOO (LOGBITP 3 (WHEN A (ASH # #))))) > ; > ; caught STYLE-WARNING: > ; The variable B is defined but never used. > > ; (ASH > ; (LOOP FOR I BELOW 0 > ; SUM 1) > ; (DOTIMES (I 1 -5) B)) > ; > ; caught STYLE-WARNING: > ; Lisp error during constant folding: > ; The function SB-C::ASH-INTO-WORD-MOD is undefined. > > debugger invoked on a SB-INT:BUG in thread > #<THREAD tid=102385 "main thread" RUNNING {1200BF0003}>: > full call to SB-C::ASH-INTO-WORD-MOD > 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/>. > > > > _______________________________________________ > 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