Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!easy!lron From: lron@easy.lrcd.com (Dwight Hubbard) Newsgroups: comp.sys.amiga.advocacy Subject: Re: 680x0 vs 80x86 Message-ID: Date: 27 Jun 91 10:30:11 GMT References: <92@ryptyde.UUCP> <4671.tnews@templar.actrix.gen.nz> <1154@stewart.UUCP> Organization: You must be talking about someone else. Lines: 22 In article <1154@stewart.UUCP> jerry@polygen.uucp (Jerry Shekhel) writes: >jbickers@templar.actrix.gen.nz (John Bickers) writes: >> >> It's usually because if you have a split cache you break programs >> that use self-modifying code. >> > >Doubtful, John, since every OS in existence treats code as data when it >loads it into memory for execution. He's right, on machines with split caches the OS will have to force a cache flush after writing the CODE data to memory. While it is no problem to modify the OS routine that loads data from disk to flush the cache, it will certainly cause problems if quite a few pieces of important software use self modifing code as they will have to be modified as well to still function. -- ---------------------------------------------------------------------- -Dwight Hubbard INTERNET: lron@easy.lrcd.com - -Kaneohe, Hawaii USENET : ...!uunet!easy!lron - - BIX : lron - ----------------------------------------------------------------------