Xref: utzoo comp.sys.amiga:37067 comp.sys.amiga.tech:6225
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!sun-barr!newstop!sun!kilowatt!raz
From: raz%kilowatt@Sun.COM (Steve -Raz- Berry)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Need information about 68010.
Keywords: 68010, 68000
Message-ID: <116365@sun.Eng.Sun.COM>
Date: 19 Jul 89 00:58:23 GMT
References: <1407@rivm05.UUCP> <116164@sun.Eng.Sun.COM> <26405@agate.BERKELEY.EDU>
Sender: news@sun.Eng.Sun.COM
Reply-To: raz@sun.UUCP (Steve -Raz- Berry)
Followup-To: comp.sys.amiga.tech
Organization: Sun Microsystems, Mountain View
Lines: 45

In article <26405@agate.BERKELEY.EDU> mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) writes:
)>In article <116164@sun.Eng.Sun.COM> raz@sun.UUCP (Steve -Raz- Berry) writes:
)><In article <1407@rivm05.UUCP> ccemdd@rivm.UUCP (Marco Dedecker) writes:
)<>I own an A500, and I would like to know if there is someone that has
)<>replaced his 68000 by an 68010.

)<3 line instruction cache. This allows very small loops to execute 
)<internal to the chip. It's effect however is nearly nil except in 
)<very rare cases.

)Only if you use the wrong compiler :-). Lattice 5.0 can be told to
)generate optimal code for the '0x0, x = 0, 1, 2, 3. Default is to
)generate code for "all", whatever that means.

Hey, watch it. Astec is coming out with V5.0 RSN ;-(

)In reality, most any simple operation on a block of memory (like copying it,
)or searching for a value) can be written to land in that cache. This
)means that those operations don't wait for intermediate instruction
)fetches, and get to run at memory speed (much nicer than an unnamed
)architechtures "block move instructions"; also more usefull).

Gee, I thought that was what the blitter was for :-) Can you show me
examples of how Lattice optimizes code for the '010? I can't think of
hardly anything else that such a small cache could be used for besides
block moves. What kind of tight loop uses only three words?

)<One caveat, I had MASSIVE problems with my system with a '010 and the
)<FFS when 1.3 came out. This turned out to be a problem with the '010
)<itself and was fixed by replacing the chip with the original 68K.

)Note that the tighter specs on the '010 make the converse more likely
)to be true. Converting to a ceramic '010 is a recommended step when
)dealing with the "double expansion guru blues."

I think you misunderstood me. I *did* blame the '010 (for being
fried).  I would have prefered a ceramic part, but hey, it was free.
I was just trying to impress upon the need for caution.

)Come all you rolling minstrels,				Mike Meyer

----
Steve -Raz- Berry      Disclaimer: I didn't do nutin!
UUCP: sun!kilowatt!raz                    ARPA: raz%kilowatt.EBay@sun.com
KILOWATT: sun!kilowatt!archive-server     archive-server%kilowatt.EBay@sun.com