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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,86ec22e070e319c0 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: How do I get this to work?? Date: 1999/01/10 Message-ID: <36993523.2075072@news.pacbell.net>#1/1 X-Deja-AN: 431064937 References: <76s0dp$1v4$1@nntp3.uunet.ca> <76tbvv$ba5$1@nntp3.uunet.ca> <36926c54.2583014@news.pacbell.net> <76uvjt$o0f$1@nnrp1.dejanews.com> <369308b4.42620270@news.pacbell.net> <771ash$rr3$1@nnrp1.dejanews.com> <36943353.31256483@news.pacbell.net> <7798bs$i9f$1@nnrp1.dejanews.com> <369850a6.31871728@news.pacbell.net> <77abdp$d5e$1@nnrp1.dejanews.com> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.pbi.net 916012491 207.214.211.214 (Sun, 10 Jan 1999 15:54:51 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Sun, 10 Jan 1999 15:54:51 PDT Newsgroups: comp.lang.ada Date: 1999-01-10T00:00:00+00:00 List-Id: >segmentation is present in the PII, for >compatibility purposes, and used in some limited manners in >the operating system kernel How could one write such operating system kernel code with a compiler that did not recognize the existence of segmented addresses? (Other than using asm code.) > Ada 95 *does* provide >a linear address model via the Integer_Address type in >System.Storage_Elements Besides the use of segments in the 8086 as a way of partially caching memory address, and its additional use in the 286/B5500 et al for protection and virtual memory, what about things like bank memory architectures (eg, CDC160-A/8090 to name one)? What does System.Storage_Elements."-" do when the two addresses are in different distributied partitions, potentially on different machines? Raise Program_Error, depending on where the partitions happen to reside? I hope not. >C does NOT provide a >linear view of the address space, so general address >arithmetic is not possible in C I sure wish I had a penny for each C programmer who believes that in char a[10],b; 'b' is the same as a[10]. And of course the 'buffer overflow' security holes demonstrate that is usually a correct assumption. >assuming *you* know the 5500 architecture well A long time ago, as an RA in the U of Wisconsin Computer Center, most of my job was maintaining and enhancing the OS on their B5500s.