Re: bug in CMPPTRT

> If I understand correctly, CMPPTRT compares pointer type, not pointer
> values.
> Second operand null means "there is no pointer here".
> So result of first CMPPTRT means, that P is a pointer (it was initialized
> to bad value - probably NULL pointer, but still a pointer), and result of
> second CMPPTRT means that Q is not a pointer (was not initialized - only
> memory allocated).

The actual statement is:
if operand 2 is null (Gene's is) an equal condition occurs if a pointer does
not exist in the storage area identified by operand 1

Nothing about the pointer being valid or the object actually existing.
If you look at the generated code, you'll see that it only checks to
see if the appropriate bits are set in the upper 64 bits of the pointer.

In Gene's case, these bits are set for P (by the INIT) not for Q (no INIT),
hence...


+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---