Re: Y21C Bug

[Mats Weber <matsw@mail.com>]

Robert A Duff wrote:

> I thought "commit on use" (or "zero on use") meant that (as in your
> example below), virtual memory is allocated, but physical memory is not.
> Then, a read or write of that memory will trap, and the operating system
> will gin up an all-zeros page of memory.

That is what is happening on most modern systems. For instance when you
start an executable, it is mapped to virtual memory but not read into
memory. Then execution is transferred to a virtual memory address within
the mapped executable, causing a page fault which loads a few pages from
the executable, and so on. So, if you don't use some pages of code, they
will never get loaded.

> Still nobody has answered my question about which operating systems
> support these fancy things.

It works that way on VMS (that I know for sure) and most Unices and NT.
Even the current MacOS uses that scheme for loading executables.

> On the other hand, I once wrote something like:
> 
>     X: array(1..One_Zillion) of Integer := (others => 0);
> 
> and the DEC Ada compiler blew up at compile time, apparently trying to
> be clever at run time.

DEC Ada creates the allocator in the object file if everything is
static. That's why you can't compile this.