public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@stanford.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: bootstrap/3163 Date: Wed, 13 Jun 2001 20:36:00 -0000 [thread overview] Message-ID: <20010614033602.6164.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR bootstrap/3163; it has been noted by GNATS. From: "Zack Weinberg" <zackw@stanford.edu> To: Robert Lipe <robertlipe@usa.net> Cc: gcc-gnats@gcc.gnu.org, john@Calva.COM Subject: Re: bootstrap/3163 Date: Wed, 13 Jun 2001 20:33:38 -0700 On Wed, Jun 13, 2001 at 11:45:25AM -0500, Robert Lipe wrote: > 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. That sentence is in everybody's mmap(2), but not everybody's mmap leaves one page between each successive anonymous mapping. The test is, however, too picky. I originally wrote it to exercise every last detail of a Cygwin runtime bug. I've seen problem reports go by for it on Solaris 8 and the Hurd as well as UnixWare 7.1.1. Fixing it just hasn't been very high on my list. It would probably be better to check for the buggy versions of Cygwin instead. I don't know how to do that reliably, or which version is the earliest in which the bug was fixed. See thread at http://gcc.gnu.org/ml/gcc-bugs/2000-11/msg00588.html . -- zw I now propose to do a little a priorizing of my own. -- Jerry Fodor, _The Mind Doesn't Work That Way_
next reply other threads:[~2001-06-13 20:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-13 20:36 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-14 0:36 bootstrap/3163 John Hughes 2001-06-13 9:46 bootstrap/3163 Robert Lipe
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=20010614033602.6164.qmail@sourceware.cygnus.com \ --to=zackw@stanford.edu \ --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: linkBe 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).