gcc mmap test fails on Solaris

[Casper Dik <Casper dot Dik at holland dot sun dot com>]

The gcc configure mmap code believes that multiple calls
you mmap for single pages return adjactent space.

Solaris does not:

test 3 nonconsecutive pages - ff380000, ff360000

(Solaris keeps a redzone between allocations)


I'm not sure gcc needs this; it is certainly not portable nor
guaranteed by any standard;

/* 3. If we map two adjacent 1-page regions and unmap them both with
   one munmap, both must go away.

   Getting two adjacent 1-page regions with two mmap calls is slightly
   tricky.  All OS's tested skip over already-allocated blocks; therefore
   we have been careful to unmap all allocated regions in previous tests.
   HP/UX allocates pages backward in memory.  No OS has yet been observed
   to be so perverse as to leave unmapped space between consecutive calls
   to mmap.  */


I suppose that makes Solaris that perverse.

This shouldn't make the mmap() test fail; it should just skip test 3.

Casper