From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Brian Drummond Newsgroups: comp.lang.ada Subject: Re: Ada 2012 Constraints (WRT an Ada IR) Date: Wed, 7 Dec 2016 22:55:40 -0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <47366b42-c0a3-41bf-a44a-5241c109d60f@googlegroups.com> <58f477d2-8b01-4001-bad8-47ea73424f4c@googlegroups.com> <6e206c3b-d4a8-44ab-9e0e-adb0924983ef@googlegroups.com> <10e8cb52-1cbd-40ed-ba11-f474c2263ced@googlegroups.com> <84oe4cdv010g9fba0jrjv2os7c0halucd0@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 7 Dec 2016 22:55:40 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="e60c8249ec6a99162373cb6305315e0c"; logging-data="12800"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18N21txoVtQMx47/ClxeXC4sAY84PS6p3o=" User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT b8fc14e git.gnome.org/git/pan2) Cancel-Lock: sha1:QCscjYq+Rv1YvMBMqmFMDNOCGE8= Xref: news.eternal-september.org comp.lang.ada:32667 Date: 2016-12-07T22:55:40+00:00 List-Id: On Wed, 07 Dec 2016 08:10:59 -0500, Dennis Lee Bieber wrote: > On Wed, 7 Dec 2016 08:36:18 +0200, Niklas Holsti > declaimed the following: > >>I don't know enough about the iAPX432 to compare the protection levels, >>but it seems that the Mill will catch a lot of the common protection >>violations and other undefined behaviour in C programs. >> > I'd have to dig up the hard-cover book I'd bought in the 80s covering > the iAPX432. For the time period, the processor had to be split into two > separate chips -- something like one to do the security checks before > passing the fetched data/code to the execution unit; couldn't fit it all > into one piece of silicon. Worse than that ... it had to push everything across a 16-bit bus between the two chips! Slightly bigger silicon and slightly more pins per package, and it would have been exponentially faster. The Linn Rekursiv, only a decade later, was able to use 299 pin packages and a 128-bit wide microcode word coordinating up to 40 small functional units in parallel - had that been available to the 432's designers it would have been a lot faster. -- Brian