public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Robert Lipe <robertlipe@usa.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: bootstrap/3163
Date: Wed, 13 Jun 2001 09:46:00 -0000	[thread overview]
Message-ID: <20010613164606.20574.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR bootstrap/3163; it has been noted by GNATS.

From: Robert Lipe <robertlipe@usa.net>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, john@Calva.COM,
        gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/3163
Date: Wed, 13 Jun 2001 11:45:25 -0500

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3163&database=gcc
 
                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.
 
 This is actually documented behaviour.   From the mmap man page:
 
    References to pages in a mapped region which are beyond the
    page containing the end of a file will result in the delivery of a
    SIGBUS signal.
 
 It sounds like this test is looking for several undocumented 
 characteristics of mmap that just happen to be true on some systems
 and not a general case mmap.  Since the code provides a reasonable
 fallback, does this cause an actual problem or is it an observation
 that this test is failing becuase the OS doesn't satisfy the 
 characteristics wanted by this test?


             reply	other threads:[~2001-06-13  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13  9:46 Robert Lipe [this message]
2001-06-13 20:36 bootstrap/3163 Zack Weinberg
2001-06-14  0:36 bootstrap/3163 John Hughes

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=20010613164606.20574.qmail@sourceware.cygnus.com \
    --to=robertlipe@usa.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).