"README.md" did not exist on "611a9c65e30303b9654cf1200d03b1c29088a35c"
- Jan 01, 2007
-
-
cshapiro authored
-
- Sep 15, 2005
-
-
rtoy authored
.indent.pro.
-
- Jan 13, 2005
-
-
fgilham authored
lisp.c into the correct <foo>-os.h files.
-
- Jul 07, 2004
-
-
rtoy authored
* backtrace.c, save.c: fprintf warnings. * interrupt.h: Declare build_fake_control_stack_frame and interrupt_handle_space_overflow. * os-common.c: Include interrupt.h to define build_fake_control_stack_frame. * parse.c, runprog.c, search.c: Include some standard system headers to get rid of undefined function warnings.
-
rtoy authored
-
- Nov 25, 1997
-
-
dtc authored
of no utility and wasn't even being maintained thoroughly. Can now use pseudo atomic in C code. All interrupt contexts are saved, even those that occur when running foreign C code; this may be necessary for reliable stack parsing on some operating systems, e.g. Linux. When the pending interrupt from a GC trigger is processed by interrupt_handle_pending, any other accumulated pending interrupt is also processed even if *interrupts-enabled* is false, breaking the behaviour of the *interrupts-enabled* flag. The best way around this for the x86 port is to call maybe-gc directly from the allocation routines; remove the recently introduced function set_maybe_gc_pending which also had other problems. Note this problem will likely occur on the other ports.
-
- Nov 19, 1997
-
-
dtc authored
GC when it reaches its trigger within pseudo atomic so that maybe_gc is called at the end of pseudo atomic.
-
- Oct 24, 1994
- Jul 27, 1993
-
-
hallgren authored
-
- Jan 13, 1993
-
-
cvs2git authored
-
- Sep 08, 1992
-
-
wlott authored
sigcontext. Hence interrupt_maybe_gc need to take them as arguments.
-
- Jul 28, 1992
-
-
wlott authored
-