From f5f749c8d180886902f0f4a2c993f8c0c302f31e Mon Sep 17 00:00:00 2001 From: Daniel Barlow Date: Thu, 18 Jul 2002 16:49:38 +0000 Subject: [PATCH] 0.7.5.16: on targets that use the stop'n'copy gc, fix the "gc trigger mysteriously ends up unset after MAYBE-GC doesn't" workaround, to put the new barrier near the end of dynamic space instead of leaving it only a page away. --- src/runtime/interrupt.c | 5 ++--- version.lisp-expr | 2 +- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/src/runtime/interrupt.c b/src/runtime/interrupt.c index 1eb49ca..68c5fe0 100644 --- a/src/runtime/interrupt.c +++ b/src/runtime/interrupt.c @@ -550,9 +550,8 @@ interrupt_maybe_gc(int signal, siginfo_t *info, void *void_context) * have to do it ourselves. Add small amount of space * to tide us over while GC is inhibited */ - set_auto_gc_trigger((u32)dynamic_space_free_pointer - -(u32)current_dynamic_space - +(u32)os_vm_page_size); + set_auto_gc_trigger(DYNAMIC_SPACE_SIZE + -(u32)os_vm_page_size); } return 1; } else { diff --git a/version.lisp-expr b/version.lisp-expr index aae9b1e..32a9b6a 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -18,4 +18,4 @@ ;;; for internal versions, especially for internal versions off the ;;; main CVS branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"0.7.5.15" +"0.7.5.16" -- 1.7.10.4