;;; In sbcl-0.6.10, Douglas Brebner reported that (SETF EXTERN-ALIEN)
;;; was messed up so badly that trying to execute expressions like
;;; this signalled an error.
-(setf (sb-alien:extern-alien "gencgc_oldest_gen_to_gc" sb-alien:unsigned)
- (sb-alien:extern-alien "gencgc_oldest_gen_to_gc" sb-alien:unsigned))
+(setf (sb-alien:extern-alien "current_control_stack_pointer" sb-alien:unsigned)
+ (sb-alien:extern-alien "current_control_stack_pointer" sb-alien:unsigned))
+
+;;; bug 133, fixed in 0.7.0.5: Somewhere in 0.pre7.*, C void returns
+;;; were broken ("unable to use values types here") when
+;;; auto-PROCLAIM-of-return-value was added to DEFINE-ALIEN-ROUTINE.
+(sb-alien:define-alien-routine ("free" free) void (ptr (* t) :in))
+
+;;; Types of alien functions were being incorrectly DECLAIMED when
+;;; docstrings were included in the definition until sbcl-0.7.6.15.
+(sb-alien:define-alien-routine ("getenv" ftype-correctness) c-string
+ "docstring"
+ (name c-string))
+
+(multiple-value-bind (function warningsp failurep)
+ (compile nil '(lambda () (ftype-correctness)))
+ (assert warningsp))
+
+(multiple-value-bind (function warningsp failurep)
+ (compile nil '(lambda () (ftype-correctness "FOO")))
+ (assert (not warningsp)))
+
+(multiple-value-bind (function warningsp failurep)
+ (compile nil '(lambda () (ftype-correctness "FOO" "BAR")))
+ (assert warningsp))
;;; success
(quit :unix-status 104)