Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!venera.isi.edu!rod
From: rod@venera.isi.edu (Rodney Doyle Van Meter III)
Newsgroups: comp.sys.amiga
Subject: Re: Whats wrong with self Modifying Code?
Message-ID: <14280@venera.isi.edu>
Date: 13 Jul 90 21:31:21 GMT
References: <24379@snow-white.udel.EDU> <6171@helios.ee.lbl.gov>
Reply-To: rod@venera.isi.edu (Rodney Doyle Van Meter III)
Organization: Information Sciences Institute, Univ. of So. California
Lines: 17


I understand WHY self-modifying code won't work, but nobody has said
HOW to get around it, assuming you're compiling code into memory to
be executed.

Is there a way to simply flush the caches that won't take a gazillion
bus cycles? I work in an interactive compiled environment, so we need
to do something like this once per user input: accept it, compile it
to a (fixed) memory space well apart from the compiler itself, then
jump to it, and, eventually, return to the user input routine. A cache
flush might be okay, if it takes less than 50 milliseconds or so.
Simply turning the caches off is unlikely to be an acceptable solution.

We're hoping to hit the 68030 (Suns fist, then I'm pushing for Amiga),
then the MIPS box.

				--Rod