Supporting ada memory management in the iAPX-432

  • Authors:

  • Fred J. Pollack;George W. Cox;Dan W. Hammerstrom;Kevin C. Kahn;Konrad K. Lai;Justin R. Rattner

  • Affiliations:

  • Intel Corporation, Aloha, Oregon;Intel Corporation, Aloha, Oregon;Intel Corporation, Aloha, Oregon;Intel Corporation, Aloha, Oregon;Intel Corporation, Aloha, Oregon;Intel Corporation, Aloha, Oregon

  • Venue:
  • ASPLOS I Proceedings of the first international symposium on Architectural support for programming languages and operating systems
  • Year:
  • 1982

Quantified Score

Hi-index 0.00

Visualization

Abstract

In this paper, we describe how the memory management mechanisms of the Intel iAPX-432 are used to implement the visibility rules of Ada. At any point in the execution of an Ada® program on the 432, the program has a protected address space that corresponds exactly to the program's accessibility at the corresponding point in the program's source. This close match of architecture and language did not occur because the 432 was designed to execute Ada—it was not. Rather, both Ada and the 432 are the result of very similar design goals. To illustrate this point, we compare, in their support for Ada, the memory management mechanisms of the 432 to those of traditional computers. The most notable differences occur in heap-space management and multitasking. With respect to the former, we describe a degree of hardware/software cooperation that is not typical of other systems. In the latter area, we show how Ada's view of sharing is the same as the 432, but differs totally from the sharing permitted by traditional systems. A description of these differences provide some insight into the problems of implementing an Ada compiler for a traditional architecture.