Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!shakti!shri From: shri@ncst.ernet.in (H.Shrikumar) Newsgroups: comp.lang.forth Subject: Re: FORTH ENTINGES/ APL 32 bit Summary: Please publish "main stream" Keywords: SC32, stack CPU Message-ID: <1180@shakti.ncst.ernet.in> Date: 13 Dec 90 17:07:43 GMT References: <2002.UUL1.3#5129@willett.pgh.pa.us> <1990Nov26.155122.28988@aplcen.apl.jhu.edu> <1139@shakti.ncst.ernet.in> <1990Dec9.042828.18170@aplcen.apl.jhu.edu> Reply-To: shri@ncst.ernet.in (H.Shrikumar ) Organization: National Centre for Software Technology, Bombay, INDIA Lines: 39 In article <1990Dec9.042828.18170@aplcen.apl.jhu.edu> john@aplcomm.jhuapl.edu (John Hayes) replies : >> There is one paper in ACM/ASPLOS-II Conference (An Architecture >> for direct execution of FORTH - John Hayes, Marty Fraeman et al). I >> assume the SC32 is a mature descendant of this 4um, 1.5MHz MOSIS >> prototype part. > >You are right. The SC32 is our third generation Forth microprocessor. [deletion] >We haven't published anything in any "main stream" journals. > >During the design of the SC32, I did a lot of stack caching >simulations. I found that the cut-back-K algorithm analyzed in [deletion] >My new analysis concludes that K=1 is optimal: When the stack >cache (buffer) is full, write out one value and when the cache >(buffer) is empty, read in one value. We are so confident about >this algorithm that we implemented it in hardware on the SC32. Wow! This is most interesting! I think this is true for embedded control programs like I suppose yours are, but is it also true for more general purpose programs? >I have written a detailed paper (which is still looking for a home) >on this study. A summary appears in the JFAR paper mentioned above. In the light of "need to present Forth to academic community at large" thread, please please do try and publish in more "main stream" journals! JFAR, and Forth Dimensions are not read by so many, and those who read are already "converted" anyway !! I await the publication of the paper. >John R. Hayes john@aplcomm.jhuapl.edu -- shrikumar ( shri@ncst.in )