[Info-vax] VAX VMS going forward

[John Dallman]

In article <a70fdb4e-86b8-48fe-a8a1-0b1f45610820o at googlegroups.com>,
xyzzy1959 at gmail.com (John Reagan) wrote:

> On Tuesday, July 28, 2020 at 1:49:14 PM UTC-4, Stephen Hoffman 
> > 32-bit or 64-bit pointer selection in various compilers, BASIC 
> > was still 32-bit when last I checked, and the thicket of APIs on 
> > OpenVMS is a confusing mash-up of 32-bit and 64-bit and mixed-bit 
> > calls.

> I'll agree 100% that the various APIs and having to remember 
> malloc32 vs malloc64 if you want to have a combo C program (and
> unfortunately you do when dealing with many/most VMS APIs).

I work for an ISV that used to support VMS on VAX and Alpha, although we
gave it up over twenty years ago. With VMS x86 happening, I started
reading this newsgroup to learn a bit about it, in case we started
getting demand for support. The product is a mathematical modelling
library, to be used in third-party ISVs' applications.

In the old days, on Alpha machines with about 128MB of RAM, everything
could be in P0 without problems, and we regarded it as a 32-bit
environment running on a 64-bit processor. Nowadays, 4GB is far too
restrictive, so confining ourselves to P0 would be impractical. The code
is C, generated from a domain-specific language. 

Can anyone point me to documentation about how malloc32 and malloc64
relate to P0, P1 and P2? 

Thanks, 

John