public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: john@Calva.COM
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/3163: gcc/aclocal.m4 mmap test fails on UnixWare 7.1.1
Date: Wed, 13 Jun 2001 04:46:00 -0000 [thread overview]
Message-ID: <200106131137.f5DBb1x26822@oceanic.CalvaEDI.COM> (raw)
>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:
next reply other threads:[~2001-06-13 4:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 4:46 john [this message]
2002-02-23 18:59 Craig Rodrigues
2003-05-09 8:29 Dara Hazeghi
2003-05-09 15:21 bangerth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200106131137.f5DBb1x26822@oceanic.CalvaEDI.COM \
--to=john@calva.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).