🚀 go-pugleaf

In article <5347@lanl.gov> jlg@lanl.gov (Jim Giles) writes:

>                                       Even on a PC, it's possible
>to implement pointers so that they can be compared no matter where
>they point (it just means that pointer compares are a little
>slower).  This should have been required by the standard.
 [...]
>J. Giles

Nice try, but unless you either (a) assume that the compiler is always 
emitting Ring 0 code, or (b) build in some very nonportable system calls
(and talk about SLOWER!), then there is no way to determine where the 
referents of two pointers are.  Both approaches require access to the 
segmentation mechanism (let alone the paging mechanism, which we'll ignore 
since your reference is to linear addresses).  Also, the results are 
volatile: even if you _do_ generate Ring 0 code, by the time the comparison 
is checked one of the segments may have moved.

Note that this argument applies to _any_ segmented memory architecture. 
The ANSI C standard could, of course, have jumped into the architecture
wars by specifying an underlying memory model.  (Why stop there?  How about
a language-defined byte order, too?)  If the standard _had_ explicitly 
excluded the 80x86 family, this whole discussion would be moot, since the 
standard would have been a dead letter.  C'est la guerre.
-- 
| The above opinions may not be original, but they are mine and mine alone. |
|            "While it may not be for you to complete the task,             |
|                 neither are you free to refrain from it."                 |
+-=-=-    (I wish this _was_ original!)        D. C. Sessions          -=-=-+