GNAT and Memory Maps?

[Freejack <Freejack@nomail.com>]

I've been picking through the GNAT docs (and Ada docs in general) in an
attempt to figure out how/if and when/why the Ada compiler might choose to
use an mmap system call in deference to a malloc/calloc or alloca call.

Basically, I'm doing some low level routines and I need explicit control
over what pages are swapped and when. ( mmap() mlock() munlock() and
munmap() are the usual C functions for handling this.)

I'm using Linux at the moment, and I could just as easily use the native C
library (glibc). However, I want to handle this entirely in Ada. I'm using
the No_Run_Time Pragma.

Note: I'm also a Forther, so the idea of explicit memory and device
handling doesnt frighten me. ;->

(Hmmm...now theres an experiment to try sometime. A Subroutine Threaded
Forth VM in Ada.)

Any references would be appreciated.

Freejack