public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@attbi.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/3163: gcc/aclocal.m4 mmap test fails on UnixWare 7.1.1 Date: Sat, 23 Feb 2002 18:59:00 -0000 [thread overview] Message-ID: <20020224025608.31654.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/3163; it has been noted by GNATS. From: Craig Rodrigues <rodrigc@attbi.com> 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: gcc/aclocal.m4 mmap test fails on UnixWare 7.1.1 Date: Sat, 23 Feb 2002 21:56:20 -0500 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3163 john@calva.com posted this info in PR 3162: libiberty/aclocal.m4 has a check to see if strncmp runs off the end of the string. It incorrectly fails on systems where MAP_ANON(YMOUS) must be used without an open fd, for example UnixWare 7.1.1. --- libiberty/aclocal.m4.orig Wed Nov 22 09:32:26 2000 +++ libiberty/aclocal.m4 Wed Jun 13 12:48:35 2001 @@ -21,8 +21,6 @@ #ifndef MAP_ANON #ifdef MAP_ANONYMOUS #define MAP_ANON MAP_ANONYMOUS -#else -#define MAP_ANON MAP_FILE #endif #endif @@ -39,6 +37,10 @@ { #if defined(HAVE_MMAP) || defined(HAVE_MMAP_ANYWHERE) char *p; +#ifdef MAP_ANON + p = (char *) mmap (0, MAP_LEN, PROT_READ|PROT_WRITE, + MAP_ANON|MAP_PRIVATE, -1, 0); +#else int dev_zero; dev_zero = open ("/dev/zero", O_RDONLY); @@ -46,7 +48,8 @@ exit (1); p = (char *) mmap (0, MAP_LEN, PROT_READ|PROT_WRITE, - MAP_ANON|MAP_PRIVATE, dev_zero, 0); + MAP_FILE|MAP_PRIVATE, dev_zero, 0); +#endif if (p == (char *)-1) exit (2); else
next reply other threads:[~2002-02-24 2:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-23 18:59 Craig Rodrigues [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-09 15:21 bangerth 2003-05-09 8:29 Dara Hazeghi 2001-06-13 4:46 john
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=20020224025608.31654.qmail@sources.redhat.com \ --to=rodrigc@attbi.com \ --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).