GC-DAEMON and nointerrupt mode?

[JONL at MIT-MC (Jon L White)]

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.