[Info-vax] Calling LIBOTS routines above ASTDEL

[John Reagan]

On Friday, April 19, 2019 at 12:03:14 PM UTC-4, osuv... at gmail.com wrote:
> I was looking at some inner mode code and saw the author had called OTS$MOVE to copy a buffer after raising IPL to driver fork. The code wasn't explicitly calling it but was doing so by way of the C compiler treating memcpy() as intrinsic. LIBOTS is usually installed resident, does that mean it's in non-pageable memory?

There are copies of almost all of the LIBOTS/OTS$ routines linked directly into the base image.  They are needed by C (and BLISS and Macro) code long before we could load any shareable image.  Code linked /SYSEXE will use the ones inside the base image (you can confirm that in the .MAP file)