"NULL-ALIEN"
"SAP-ALIEN" "SHORT" "SIGNED" "SLOT" "STRUCT"
"UNDEFINED-ALIEN-ERROR"
+ "UNLOAD-SHARED-OBJECT"
"UNSIGNED"
"UNSIGNED-CHAR" "UNSIGNED-INT" "UNSIGNED-LONG" "UNSIGNED-LONG-LONG" "UNSIGNED-SHORT"
"UTF8-STRING"
"ENTRY-NODE-INFO-NLX-TAG" "ENTRY-NODE-INFO-ST-TOP"
"PHYSENV-DEBUG-LIVE-TN" "PHYSENV-LIVE-TN"
"FAST-SYMBOL-VALUE"
+ "FIND-SAVED-FP-AND-PC"
"FIXUP-NOTE-KIND"
"FIXUP-NOTE-FIXUP"
"FIXUP-NOTE-POSITION"
;; are assertions" default
"TRULY-THE"
+ ;; Misc. array and vector tools.
+ "SIMPLE-ARRAY-VECTOR"
+
;; This is something which must exist inside any Common
;; Lisp implementation, and which someone writing a
;; customized toplevel might well want. It seems perverse
"OUTPUT-SYMBOL-NAME" "%COERCE-NAME-TO-FUN"
"INVOKE-MACROEXPAND-HOOK" "DEFAULT-STRUCTURE-PRINT"
"LAYOUT" "LAYOUT-LENGTH" "LAYOUT-PURE" "DSD-RAW-TYPE"
- "DEFSTRUCT-DESCRIPTION" "UNDEFINE-STRUCTURE" "DD-COPIER"
+ "DEFSTRUCT-DESCRIPTION" "UNDECLARE-STRUCTURE" "DD-COPIER"
"UNDEFINE-FUN-NAME" "DD-TYPE" "CLASSOID-STATE" "INSTANCE"
"*TYPE-SYSTEM-INITIALIZED*" "FIND-LAYOUT" "DSD-NAME"
"%TYPEP" "DD-RAW-INDEX" "DD-NAME" "CLASSOID-SUBCLASSES"