Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Commit [0c08cc] Maximize Restore History

Fix CHAR-EQUAL on base-chars on non-sb-unicode.

BASE-CHAR-P, called by TWO-ARG-CHAR-EQUAL, isn't properly implemented
on non-sb-unicode, the transform by which it gets transformed into
(typep x 'base-char) is disabled, causing an infinite loop.
Since testing for base-char-p is usually redundant on #-sb-unicode,
don't define it there at all. This will catch inadvertent uses.
In the few places where it's currently used, it's can be safely
omitted.

Reported by Jan Moringen.

Stas Boukarev Stas Boukarev 2013-09-09

changed src/code/pred.lisp
changed src/code/target-char.lisp
changed src/compiler/generic/vm-fndb.lisp
changed src/compiler/generic/vm-tran.lisp
changed src/compiler/x86-64/insts.lisp
changed src/compiler/x86/insts.lisp
src/code/pred.lisp Diff Switch to side-by-side view
Loading...
src/code/target-char.lisp Diff Switch to side-by-side view
Loading...
src/compiler/generic/vm-fndb.lisp Diff Switch to side-by-side view
Loading...
src/compiler/generic/vm-tran.lisp Diff Switch to side-by-side view
Loading...
src/compiler/x86-64/insts.lisp Diff Switch to side-by-side view
Loading...
src/compiler/x86/insts.lisp Diff Switch to side-by-side view
Loading...