bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin

[Werner Tuchan]

>
> Weird.  The bytes after EOF are a mixture of NULs and 0xc0.  Is 0xc0
> of special significance in Windows?  Is your version of cygwin the
> latest?  I recall some talk about mmap bugs in cygwin.
>

The cygwin version is pretty recent. Two weeks old or so. The data after EOF
is only garbage. I've seen different values than 0x0 or 0xc0 in the error
messages. Windows propably doesn't clear the page before mapping the file
onto it. There is likely a different behaviour here between Windows ME and
NT.