From: Arpadffy Zoltan <[email protected]>
> It is interesting that not forcing the /pointer_size=3D64 - the build is OK=
> (by running @makevms all "" nodebug)
Interesting, perhaps, but not really news.
HELP CC /POINTER_SIZE
[...]
Specifying /POINTER_SIZE=32 directs the compiler to assume that all
pointers are 32-bit pointers. But unlike the default of
/NOPOINTER_SIZE, /POINTER_SIZE=32 enables use of the #pragma
pointer_size long and #pragma pointer_size short preprocessor
directives to control pointer size throughout your program.
[...]
> Until now, I believed that DCC will use 64-bit pointers on a 64-bit archite=
> cture when the pointer size is not explicitly specified.
If "DCC" is anything like DEC/Compaq/HP C, then no, as documented.
> Seems, there is some kind of smart cast around descriptors when not explici=
> tly specified that the pointers' size is 64-bit.
HELP CC Language_topics Preprocessor #pragma
Look for "pointer_size".
> It is time to dig deeper into the literature.
The time for that might actually have been near when you were first
thinking about saying "/POINTER_SIZE = 64".
Note that (as I read the stuff) most of the RMS structures, including
FAB and NAM[L], support only 32-bit pointers/descriptors, so all those
file names can't use 64-bit pointers/descriptors. I took a quick look
at this stuff and decided that some thought would be needed to decide
how to make it work. I suspect that some string copying will be needed
for the RMS stuff.
------------------------------------------------------------------------
Steven M. Schweda sms@antinode-info
382 South Warwick Street (+1) 651-699-9818
Saint Paul MN 55105-2547
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
