Hello Steven,

> The time for that might actually have been near when you were first
thinking about saying "/POINTER_SIZE = 64".

Yes, you are right... I was running ahead without learning enough about the 
topic.

Then, after all, I think, the best solution would be to leave as it is and 
close this (#2449) issue.

We can continue to live with default (/NOPOINTER_SIZE) and optional 32-bit 
build (/POINTER_SIZE=32)

Maybe, it would be useful to change the makevms.com script that do not allow 
/POINTER_SIZE=64 parameter, but in those cases change that to /NOPOINTER_SIZE 
instead.

What is your opinion?

Regards,
Z

-----Original Message-----
From: Steven M. Schweda [mailto:s...@antinode.info]
Sent: den 15 februari 2011 14:48
To: openssl-dev@openssl.org
Subject: Re: [openssl.org #2449] [BUG] openssl 1.0.0d warnings during build and 
ACCVIO on OpenVMS

From: Arpadffy Zoltan <zoltan.arpad...@scientificgames.se>

> 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                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org



______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to