[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GC-DAEMON and nointerrupt mode?
- To: RWK at MIT-MC
- Subject: GC-DAEMON and nointerrupt mode?
- From: JONL at MIT-MC (Jon L White)
- Date: Tue, 20 Nov 79 17:49:00 GMT
- Cc: (BUG LISP) at MIT-MC
- Original-date: 20 NOV 1979 1249-EST
Upon reconsideration, I'm thinking that the current status is ok,
namely that the so-called "synchronous" interrupts should not
fiddle with, nor care about, the state of nointerrupt. these are:
AUTOLOAD, ERRSET, *RSET-TRAP, GC-DAEMON, GC-OVERFLOW, and PDL-OVERFLOW.
Thus it would be ok to write some code which first sets "nointerrupt"
and then calls the GC - the "nointerrupt" would delay neither the
GC-OVERFLOW nor the GC-DAEMON functions; but GC-LOSSAGE is deferred
until nointerrupt is null.