diff --git a/src/code/early-alieneval.lisp b/src/code/early-alieneval.lisp
index 67478a548..5da7b5085 100644
--- a/src/code/early-alieneval.lisp
+++ b/src/code/early-alieneval.lisp
@@ -17,3 +17,12 @@
 ;;; used to keep from outputting the slots again if the same structure
 ;;; shows up twice.
 (defvar *record-types-already-unparsed*)
+
+;;; not documented in CMU CL:-(
+;;;
+;;; reverse engineering observations:
+;;;   * seems to be set when translating return values
+;;;   * seems to enable the translation of (VALUES), which is the
+;;;     Lisp idiom for C's return type "void" (which is likely
+;;;     why it's set when when translating return values)
+(defvar *values-type-okay* nil)
diff --git a/src/code/host-alieneval.lisp b/src/code/host-alieneval.lisp
index 3466981a9..bfe0b4288 100644
--- a/src/code/host-alieneval.lisp
+++ b/src/code/host-alieneval.lisp
@@ -1045,15 +1045,6 @@
 
 ;;;; the FUNCTION and VALUES alien types
 
-;;; not documented in CMU CL:-(
-;;;
-;;; reverse engineering observations:
-;;;   * seems to be set when translating return values
-;;;   * seems to enable the translation of (VALUES), which is the
-;;;     Lisp idiom for C's return type "void" (which is likely
-;;;     why it's set when when translating return values)
-(defvar *values-type-okay* nil)
-
 (define-alien-type-class (fun :include mem-block)
   (result-type (missing-arg) :type alien-type)
   (arg-types (missing-arg) :type list)
diff --git a/version.lisp-expr b/version.lisp-expr
index 23bb221d3..4a9ae389b 100644
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.9.5.64"
+"0.9.5.65"