Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
From: Christopher.Hoover@CS.CMU.EDU
Newsgroups: comp.sys.m68k
Subject: Re: mc68040 I/D coherency
Message-ID: <YaO23DC00hsj0IpwY5@cs.cmu.edu>
Date: 2 Jun 90 20:25:51 GMT
References: <765@ssp11.idca.tds.philips.nl>, <265@demott.COM>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 14
In-Reply-To: <265@demott.COM>

kdq@demott.COM (Kevin D. Quitt) writes:
> 
>     It should be impossible for any user-level code.  Priveleged code like
> a debugger must be smart enough to invalidate the cache, and that has nothing
> to do with I vs D.
> 

No, user-level code must be able to flush the I-cache.  Languages like
Lisp which manage their heaps using a copying garbage collector need
to flush the I-cache after a GC as objects containing code may be
moved by the garbage collector.

-- Chris.
(Christopher.Hoover@CS.CMU.EDU)