Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!happy.colorado.edu!kskelm
From: kskelm@happy.colorado.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 68040 Compatibility Warning
Message-ID: <1991May31.141855.1@happy.colorado.edu>
Date: 31 May 91 20:18:55 GMT
References: <22049@cbmvax.commodore.com>
Sender: news@colorado.edu (The Daily Planet)
Organization: University of Colorado, Boulder
Lines: 22
Nntp-Posting-Host: happy

In article <22049@cbmvax.commodore.com>, mks@cbmvax.commodore.com (Michael Sinz) writes:
> AmigaOS 2.0 correctly clears the caches as needed after it does
> the LoadSeg() of a program.  Applications need to do the same if
> they create code at run-time.  One such example was the article
> on multiple processes in AmigaMail.  What is needed is that just
> before the call to CreateProc() that a call to the EXEC V37
> CacheClearU() function is executed.  In C that would be:
> 

   Okay, question:  Does CacheClearU() execute a couple of special
instructions, or does it execute, say, a whole pile of NOPs, enough to "unload"
anything else that may have been in the Instruction Cache?

   What a mess.  Yours is a position I do not envy! :)

+------------------------------------------------------------+
|      ///  Kevin "Visionary will be done RSN" Kelm          |
|     ///  kskelm@happy.colorado.edu                         |
| \\\/// "Reality is subjective-- if you can make your own,  |
|  \XX/ then who's crazy? That's entertainment software!"-me |
| C code run.  Run, code, run--PLEASE!                       |
+------------------------------------------------------------+