Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end
From: seimarao@gmail.com
Newsgroups: comp.compilers
Subject: Safe Pointers at the Intermediate Language or Hardware Level
Date: Mon, 10 Feb 2014 09:11:38 -0800 (PST)
Organization: Compilers Central
Lines: 18
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <14-02-007@comp.compilers>
NNTP-Posting-Host: news.iecc.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: miucha.iecc.com 1392077462 19040 64.57.183.58 (11 Feb 2014 00:11:02 GMT)
X-Complaints-To: abuse@iecc.com
NNTP-Posting-Date: Tue, 11 Feb 2014 00:11:02 +0000 (UTC)
Keywords: code, design, comment
Posted-Date: 10 Feb 2014 19:11:02 EST
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Xref: csiph.com comp.compilers:1086

Hi,

    Its been a long time since Java & .Net introduced safe address
    types to the computing world.

    My question is have we settled on what could be a proper representation
    for safe pointers ?

    Some Mainframes like the 390 have historically supported safe pointers,
    I remember.

Sincerely,
Seima Rao.
[I looked at my S/390 Principles of Operation, and I see a bunch of stuff
for tracing, but nothing that looks like safe pointers.  I'd think it was
hardware dependent, e.g., if a machine has a fairly clean and efficient
trap for an unmapped zero address, you'd use that, but if it doesn't, you'd
do something else. -John]