🚀 go-pugleaf

In article <1990Jul10.201202.3378@sunee.waterloo.edu> gpsteffl@sunee.waterloo.edu (Glenn Patrick Steffler) writes:

   >stack-machine code to run. For large applications (popi, for instance)
   >or those where speed is more critical (your video driver), compile to
   >an array and tell the OS you're launching a task loaded into that
   >chunk of memory, and use that. The OS should take care of making sure
   >the code in that memory actually gets run, and not whatever you put
   >there last time around.

   Fine, thats what I would do if it were not for the problems that may happen
   on machines which cache lots of memory.  If I recompile into the array 
   and run code from it withouta a cache flush, the possibility of major
   problems is quite large.

The last two sentences in the paragraph cover that. You don't just
branch into the code, you run it as a seperate task (or thread or
whatever your favorite term is). If the OS fails to correctly deal
with caches in this case, then it's got a _serious_ bug. After all you
haven't done anything different from what happens when a shell starts
an application.

The OS may do a cache flush. Then again, it may not - it has more
information about what's going on in the system than you do.

	<mike
--
And then up spoke his own dear wife,			Mike Meyer
Never heard to speak so free.				mwm@relay.pa.dec.com
"I'd rather a kiss from dead Matty's lips,		decwrl!mwm
Than you or your finery."