Loading…

Supporting ada memory management in the iAPX-432

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...

Full description

Saved in:
Bibliographic Details
Published in:Computer architecture news 1982-03, Vol.10 (2), p.117-131
Main Authors: Pollack, Fred J., Cox, George W., Hammerstrom, Dan W., Kahn, Kevin C., Lai, Konrad K., Rattner, Justin R.
Format: Article
Language:English
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
cited_by cdi_FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3
cites cdi_FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3
container_end_page 131
container_issue 2
container_start_page 117
container_title Computer architecture news
container_volume 10
creator Pollack, Fred J.
Cox, George W.
Hammerstrom, Dan W.
Kahn, Kevin C.
Lai, Konrad K.
Rattner, Justin R.
description 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.
doi_str_mv 10.1145/964750.801835
format article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_miscellaneous_29445260</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>29445260</sourcerecordid><originalsourceid>FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3</originalsourceid><addsrcrecordid>eNotkD1PwzAURT2ARCmM7JnYXJ5jvyQeq4ovqRJIdGCzbOelBMVJsJOh_56iMF3dq6M7HMbuBGyEUPigC1UibCoQlcQLtgJRSI7n9Ypdp_QN515KWDH4mMdxiFPbHzNb2yxQGOIpC7a3RwrUT1nbZ9MXZe32_ZMrmd-wy8Z2iW7_c80OT4-H3Qvfvz2_7rZ77oWQwBEAZVUAao2NhrIQzjWqrOrSkfNYSmcxh5pQg7NFrWTtnXOA3pOFiuSa3S-3Yxx-ZkqTCW3y1HW2p2FOJtdKYV7AGeQL6OOQUqTGjLENNp6MAPOnwiwqzKJC_gLRTlDm</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>29445260</pqid></control><display><type>article</type><title>Supporting ada memory management in the iAPX-432</title><source>Association for Computing Machinery:Jisc Collections:ACM OPEN Journals 2023-2025 (reading list)</source><creator>Pollack, Fred J. ; Cox, George W. ; Hammerstrom, Dan W. ; Kahn, Kevin C. ; Lai, Konrad K. ; Rattner, Justin R.</creator><creatorcontrib>Pollack, Fred J. ; Cox, George W. ; Hammerstrom, Dan W. ; Kahn, Kevin C. ; Lai, Konrad K. ; Rattner, Justin R.</creatorcontrib><description>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.</description><identifier>ISSN: 0163-5964</identifier><identifier>DOI: 10.1145/964750.801835</identifier><language>eng</language><ispartof>Computer architecture news, 1982-03, Vol.10 (2), p.117-131</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3</citedby><cites>FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>314,780,784,27924,27925</link.rule.ids></links><search><creatorcontrib>Pollack, Fred J.</creatorcontrib><creatorcontrib>Cox, George W.</creatorcontrib><creatorcontrib>Hammerstrom, Dan W.</creatorcontrib><creatorcontrib>Kahn, Kevin C.</creatorcontrib><creatorcontrib>Lai, Konrad K.</creatorcontrib><creatorcontrib>Rattner, Justin R.</creatorcontrib><title>Supporting ada memory management in the iAPX-432</title><title>Computer architecture news</title><description>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.</description><issn>0163-5964</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>1982</creationdate><recordtype>article</recordtype><recordid>eNotkD1PwzAURT2ARCmM7JnYXJ5jvyQeq4ovqRJIdGCzbOelBMVJsJOh_56iMF3dq6M7HMbuBGyEUPigC1UibCoQlcQLtgJRSI7n9Ypdp_QN515KWDH4mMdxiFPbHzNb2yxQGOIpC7a3RwrUT1nbZ9MXZe32_ZMrmd-wy8Z2iW7_c80OT4-H3Qvfvz2_7rZ77oWQwBEAZVUAao2NhrIQzjWqrOrSkfNYSmcxh5pQg7NFrWTtnXOA3pOFiuSa3S-3Yxx-ZkqTCW3y1HW2p2FOJtdKYV7AGeQL6OOQUqTGjLENNp6MAPOnwiwqzKJC_gLRTlDm</recordid><startdate>198203</startdate><enddate>198203</enddate><creator>Pollack, Fred J.</creator><creator>Cox, George W.</creator><creator>Hammerstrom, Dan W.</creator><creator>Kahn, Kevin C.</creator><creator>Lai, Konrad K.</creator><creator>Rattner, Justin R.</creator><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>198203</creationdate><title>Supporting ada memory management in the iAPX-432</title><author>Pollack, Fred J. ; Cox, George W. ; Hammerstrom, Dan W. ; Kahn, Kevin C. ; Lai, Konrad K. ; Rattner, Justin R.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>1982</creationdate><toplevel>online_resources</toplevel><creatorcontrib>Pollack, Fred J.</creatorcontrib><creatorcontrib>Cox, George W.</creatorcontrib><creatorcontrib>Hammerstrom, Dan W.</creatorcontrib><creatorcontrib>Kahn, Kevin C.</creatorcontrib><creatorcontrib>Lai, Konrad K.</creatorcontrib><creatorcontrib>Rattner, Justin R.</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>Computer architecture news</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Pollack, Fred J.</au><au>Cox, George W.</au><au>Hammerstrom, Dan W.</au><au>Kahn, Kevin C.</au><au>Lai, Konrad K.</au><au>Rattner, Justin R.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Supporting ada memory management in the iAPX-432</atitle><jtitle>Computer architecture news</jtitle><date>1982-03</date><risdate>1982</risdate><volume>10</volume><issue>2</issue><spage>117</spage><epage>131</epage><pages>117-131</pages><issn>0163-5964</issn><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.</abstract><doi>10.1145/964750.801835</doi><tpages>15</tpages></addata></record>
fulltext fulltext
identifier ISSN: 0163-5964
ispartof Computer architecture news, 1982-03, Vol.10 (2), p.117-131
issn 0163-5964
language eng
recordid cdi_proquest_miscellaneous_29445260
source Association for Computing Machinery:Jisc Collections:ACM OPEN Journals 2023-2025 (reading list)
title Supporting ada memory management in the iAPX-432
url http://sfxeu10.hosted.exlibrisgroup.com/loughborough?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-08T01%3A40%3A14IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Supporting%20ada%20memory%20management%20in%20the%20iAPX-432&rft.jtitle=Computer%20architecture%20news&rft.au=Pollack,%20Fred%20J.&rft.date=1982-03&rft.volume=10&rft.issue=2&rft.spage=117&rft.epage=131&rft.pages=117-131&rft.issn=0163-5964&rft_id=info:doi/10.1145/964750.801835&rft_dat=%3Cproquest_cross%3E29445260%3C/proquest_cross%3E%3Cgrp_id%3Ecdi_FETCH-LOGICAL-c1130-500538605995f90761bbf478d7bebc573ba520de590ba6d43dcbbb05ccea08e3%3C/grp_id%3E%3Coa%3E%3C/oa%3E%3Curl%3E%3C/url%3E&rft_id=info:oai/&rft_pqid=29445260&rft_id=info:pmid/&rfr_iscdi=true