Path: utzoo!news-server.csri.toronto.edu!rutgers!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: Starting another copy of your own code Message-ID: <19852@cbmvax.commodore.com> Date: 14 Mar 91 08:48:38 GMT References: <63329@eerie.acsu.Buffalo.EDU> <19578@cbmvax.commodore.com> <06417.AA06417@babylon.rmt.sub.org> <18cb4d63.ARN0b56@swinjm.UUCP> <1991Mar9.170859.4810@Sandelman.OCUnix.On.Ca> <06493.AA06493@babylon.rmt.sub.org> <06545.AA065 Organization: Commodore, West Chester, PA Lines: 34 45@babylon.r Sender: Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Followup-To: Distribution: Organization: Commodore, West Chester, PA Keywords: In article cg@ami-cg.UUCP (Chris Gray) writes: >In article <06545.AA06545@babylon.rmt.sub.org> rbabel@babylon.rmt.sub.org (Ralp >>"dynamically-created code"? Chris, I guess you've been doing >>too much compiler development lately! :-) > >Naw - working full-time on a MUD for the Amiga - all interpreted. Hmmmm. >>It does break on CPUs with _separate_ code and data caches. > >Ok, you win - I wuz wrong. Sigh. In reality I would guess that the I-cache >is flushed by CreateProc and/or LoadSeg, so it wouldn't matter, but I agree >we are talking principles here. In 2.0, LoadSeg flushes the ICache after relocation, and CreateNewProc flushes if it has to build any code you you (NP_Entry). If you build code yourself, a quick call to CacheClearE with CACRF_ClearI will solve your day. It even takes a start location and length. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)