X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=tests%2Fgc.impure.lisp;h=1c3d9f96ded5d66eec65d12c3771db287cf6dd7d;hb=3cd0a9aafc20ce12075f38ebaed86676c922fde2;hp=ef4313af3ee7675540e14622758591aa39f4747a;hpb=ec58ac28523a2e9a296e3f84ad0928ee04842eae;p=sbcl.git

diff --git a/tests/gc.impure.lisp b/tests/gc.impure.lisp
index ef4313a..1c3d9f9 100644
--- a/tests/gc.impure.lisp
+++ b/tests/gc.impure.lisp
@@ -65,7 +65,17 @@
         (assert (= (sb-ext:generation-number-of-gcs-before-promotion i) 1))))
 
 (defun stress-gc ()
-  (let* ((x (make-array (truncate (* 0.2 (dynamic-space-size))
+  ;; Kludge or not?  I don't know whether the smaller allocation size
+  ;; for sb-safepoint is a legitimate correction to the test case, or
+  ;; rather hides the actual bug this test is checking for...  It's also
+  ;; not clear to me whether the issue is actually safepoint-specific.
+  ;; But the main problem safepoint-related bugs tend to introduce is a
+  ;; delay in the GC triggering -- and if bug-936304 fails, it also
+  ;; causes bug-981106 to fail, even though there is a full GC in
+  ;; between, which makes it seem unlikely to me that the problem is
+  ;; delay- (and hence safepoint-) related. --DFL
+  (let* ((x (make-array (truncate #-sb-safepoint (* 0.2 (dynamic-space-size))
+                                  #+sb-safepoint (* 0.1 (dynamic-space-size))
                                   sb-vm:n-word-bytes))))
     (elt x 0)))