Related articles |
---|
Safe Pointers at the Intermediate Language or Hardware Level seimarao@gmail.com (2014-02-10) |
Re: Safe Pointers at the Intermediate Language or Hardware Level flaps@dgp.toronto.edu (2014-02-11) |
Re: Safe Pointers at the Intermediate Language or Hardware Level gah@ugcs.caltech.edu (glen herrmannsfeldt) (2014-02-11) |
Re: Safe Pointers at the Intermediate Language or Hardware Level ivan@ootbcomp.com (Ivan Godard) (2014-02-10) |
Re: Safe Pointers at the Intermediate Language or Hardware Level wclodius@earthlink.net (2014-02-10) |
Re: Safe Pointers at the Intermediate Language or Hardware Level seimarao@gmail.com (Seima Rao) (2014-02-11) |
Re: Safe Pointers at the Intermediate Language or Hardware Level ivan@ootbcomp.com (Ivan Godard) (2014-02-12) |
From: | flaps@dgp.toronto.edu (Alan J Rosenthal) |
Newsgroups: | comp.compilers |
Date: | 11 Feb 2014 00:58:43 GMT |
Organization: | Compilers Central |
References: | 14-02-007 |
Keywords: | design, C, comment |
Posted-Date: | 11 Feb 2014 00:40:40 EST |
I liked the "Saber C" C interpreter a few decades ago. It had what I think
you are calling "safe pointers".
They had a paper at Usenix in I think the very-late 1980s, but in a
nutshell, every pointer value contained three addresses: the actual
address value, the lowest you were allowed to go with that pointer
value, and the highest you were allowed to go.
[Worked great, but it was an interpreter. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.