iAPX 432

Sundar R. Iyengar sundar at cwruecmp.UUCP
Tue May 6 23:50:37 AEST 1986


>> >Now, if only somebody would invent an architecture where all objects,
>> >including dynamicly allocated objects, are isolated in memory, then any
>> >subscript error would cause an immediate memory fault.
>>
>>    If I'm not mistaken, this was done on the iAPX432, using a capability-
>> based addressing scheme.  Dimmed the lights.  You could probably construct
>> such an environment on the 80286, but no one does, probably for efficiency
>> reasons.

> One problem with the 432's approach was that it was very extreme; I don't
> think it's good to say "the 432 tried these approaches and it was too slow,
> therefore the checking can't be efficiently implemented."

If I remember correctly, iAPX 432 is a vertically microcoded machine.
On top of that, the microcode is generated in one chip and then used in
another.  These two are some more reasons why iAPX is slow.

-- sri



More information about the Comp.lang.c mailing list