This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
bootstrap/3163: gcc/aclocal.m4 mmap test fails on UnixWare 7.1.1
- To: gcc-gnats at gcc dot gnu dot org
- Subject: bootstrap/3163: gcc/aclocal.m4 mmap test fails on UnixWare 7.1.1
- From: john at Calva dot COM
- Date: Wed, 13 Jun 2001 13:37:01 +0200 (CEST)
>Number: 3163
>Category: bootstrap
>Synopsis: gcc/aclocal.m4 mmap test fails on UnixWare 7.1.1
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jun 13 04:46:05 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: John Hughes
>Release: 3.0 20010611 (prerelease)
>Organization:
CalvaEDI S.A.
>Environment:
System: UnixWare oceanic 5 7.1.1 i386 x86at SCO UNIX_SVR5
host: i586-sco-sysv5uw7.1.1
build: i586-sco-sysv5uw7.1.1
target: i586-sco-sysv5uw7.1.1
configured with: ../gcc-3.0-20010611/configure --prefix=/u/local --with-local_prefix=/u/local
>Description:
To quote gcc/aclocal.m4:
/* 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. */
Well, UnixWare 7.1.1 is that perverse system. It seems to leave
one page between each mapping.
>How-To-Repeat:
configure
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: