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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.157.63.66 with SMTP id m60mr15947780otc.27.1481165083813;
        Wed, 07 Dec 2016 18:44:43 -0800 (PST)
X-Received: by 10.157.44.172 with SMTP id p41mr4839054otb.6.1481165083753;
 Wed, 07 Dec 2016 18:44:43 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!1.eu.feeder.erje.net!newspeer1.nac.net!border2.nntp.dca1.giganews.com!nntp.giganews.com!n6no4149694qtd.0!news-out.google.com!m27ni8572qtf.1!nntp.google.com!n6no4149693qtd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Wed, 7 Dec 2016 18:44:43 -0800 (PST)
In-Reply-To: <eapov3Fpu2kU1@mid.individual.net>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=67.0.242.189;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 67.0.242.189
References: <o1uj70$qe2$1@dont-email.me> <o1uroj$jsj$1@gioia.aioe.org>
 <47366b42-c0a3-41bf-a44a-5241c109d60f@googlegroups.com>
 <alpine.DEB.2.20.1612050922450.22845@debian>
 <o23a8a$11e9$1@gioia.aioe.org> <lywpfed43r.fsf@pushface.org>
 <58f477d2-8b01-4001-bad8-47ea73424f4c@googlegroups.com>
 <o24oqj$1no2$1@gioia.aioe.org>
 <6e206c3b-d4a8-44ab-9e0e-adb0924983ef@googlegroups.com>
 <o2799o$1hn5$1@gioia.aioe.org>
 <10e8cb52-1cbd-40ed-ba11-f474c2263ced@googlegroups.com>
 <84oe4cdv010g9fba0jrjv2os7c0halucd0@4ax.com>
 <eapov3Fpu2kU1@mid.individual.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0973c0e0-16ae-42c8-8ae0-d9c0e98aaf4d@googlegroups.com>
Subject: Re: Ada 2012 Constraints (WRT an Ada IR)
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Thu, 08 Dec 2016 02:44:43 +0000
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:32671
Date: 2016-12-07T18:44:43-08:00
List-Id: <comp.lang.ada>

On Tuesday, December 6, 2016 at 11:36:22 PM UTC-7, Niklas Holsti wrote:
> On 16-12-07 03:08 , Dennis Lee Bieber wrote:
> > On Tue, 6 Dec 2016 13:44:27 -0800 (PST), Shark8
> > declaimed the following:
> >
> >>
> >> One reason that an IR could be handy is as an execution model -- like =
how Intel's iAPX 432 was designed for Ada's feature-set -- having a general=
ized form for constraints/violations would mean that the the chip would onl=
y have to handle one kind of constraint-type instead of having to have spec=
ialized forms for P3 and P0.
> >>
> > 	With modern processor silicon, the iAPX432 might almost run fast enoug=
h
> > to be usable.
> >
> > 	(Was a nice idea -- but the overhead of all the protection handling
> > bogged it down too much to get a foot-hold, or even a hand-hold <G>)
>=20
> There's a new processor architecture in development called "the Mill",=20
> which has a lot of protection built-in, but promises to be fast, at=20
> least in the computation-per-watt measure. See http://millcomputing.com/.
>=20
> I don't know enough about the iAPX432 to compare the protection levels,=
=20
> but it seems that the Mill will catch a lot of the common protection=20
> violations and other undefined behaviour in C programs.
>=20
> The Mill looks like a very good processor for Ada, for example all=20
> operations on integers have variants that wrap around, saturate, or=20
> trap, on over/underflow.

The Mill does look interesting; I hope that Ada can find a home on it -- an=
d that /would/ be a bit of an incentive to get another implementation up.