(defmacro define-unibyte-mapper (byte-char-name code-byte-name &rest exceptions)
`(progn
- (declaim (inline ,byte-char-name ,code-byte-name))
+ (declaim (inline ,byte-char-name))
(defun ,byte-char-name (byte)
(declare (optimize speed (safety 0))
(type (unsigned-byte 8) byte))
exception
byte))))
byte))
+ ;; This used to be inlined, but it caused huge slowdowns in SBCL builds,
+ ;; bloated the core by about 700k on x86-64. Removing the inlining
+ ;; didn't seem to have any performance effect. -- JES, 2005-10-15
(defun ,code-byte-name (code)
(declare (optimize speed (safety 0))
(type char-code code))
+ ;; FIXME: I'm not convinced doing this with CASE is a good idea as
+ ;; long as it's just macroexpanded into a stupid COND. Consider
+ ;; for example the output of (DISASSEMBLE 'SB-IMPL::CODE->CP1250-MAPPER)
+ ;; -- JES, 2005-10-15
(case code
,@(mapcar (lambda (exception)
(destructuring-bind (byte code) exception
(defparameter *external-format-functions*
'(((:ascii :us-ascii :ansi_x3.4-1968 :iso-646 :iso-646-us :|646|)
ascii->string-aref string->ascii)
- ((:latin1 :latin-1 :iso-8859-1)
+ ((:latin1 :latin-1 :iso-8859-1 :iso8859-1)
latin1->string-aref string->latin1)
#!+sb-unicode
- ((:latin9 :latin-9 :iso-8859-15)
+ ((:latin9 :latin-9 :iso-8859-15 :iso8859-15)
latin9->string-aref string->latin9)
((:utf8 :utf-8)
utf8->string-aref string->utf8)))