Path: utzoo!telly!ddsw1!lll-winken!csd4.milw.wisc.edu!dogie.macc.wisc.edu!indri!polyslo!usc!elroy!ames!sun-barr!male!pitstop!sun!david@sun.com
From: david@sun.com (J.R. ``Bob'' Dobbs)
Newsgroups: gnu.gcc
Subject: Re: Porting gcc to the new Sun SPARCstation 1 and SPARCstation 300 series
Message-ID: <102542@sun.Eng.Sun.COM>
Date: 3 May 89 06:16:10 GMT
References: <8905030323.AA27122@jato.Jpl.Nasa.Gov>
Sender: david@sun.Eng.Sun.COM
Lines: 11

In article <8905030323.AA27122@jato.Jpl.Nasa.Gov> earle@JATO.JPL.NASA.GOV
(Greg Earle - Sun Software Support) writes:
>On the other hand, the new SPARCstation machines have a write-through cache.
>Both write buffers are only one write deep.  On the SPARCstation-1, it is
>32 bits deep; on the SPARCstation/SPARCserver 300 series, it is 64 bits deep.
>Because of this, back-to-back writes can tie up the memory bus.

For the same reason, you shouldn't schedule a load right after a store.

-- 
David DiGiacomo, Sun Microsystems, Mt. View, CA  sun!david david@sun.com