Xref: utzoo comp.lang.c:9845 comp.arch:4567
Path: utzoo!yunexus!geac!daveb
From: daveb@geac.UUCP (David Collier-Brown)
Newsgroups: comp.lang.c,comp.arch
Subject: Re: volatile (in comp.lang.c)
Message-ID: <2682@geac.UUCP>
Date: 2 May 88 13:34:02 GMT
Article-I.D.: geac.2682
Posted: Mon May  2 09:34:02 1988
References: <20345@pyramid.pyramid.com> <833@mcdsun.UUCP> <9916@tekecs.TEK.COM> <2642@geac.UUCP> <2082@winchester.mips.COM> <2674@geac.UUCP> <6612@lll-winken.llnl.gov>
Reply-To: daveb@geac.UUCP (David Collier-Brown)
Organization: The G. Yac Co. Ltd. Inc. Pty.
Lines: 17


In article <6612@lll-winken.llnl.gov> brooks@lll-crg.llnl.gov.UUCP (Eugene D. Brooks III) writes:
>obviously needs further development in the context of multiprocessing.
>Perhaps this will happen in the second "standards cycle" for C.  With all
>the VLSI based multiprocessors hitting the market, good language support
>for them will become very important.

  Yup.
  The Sequent is probably a good example: their cache algorithms are
subtle and (seemingly) elegant

--dave c-b
-- 
 David Collier-Brown.                 {mnetor yunexus utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind) 
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.