public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/98300] GCC 11 failed to build on Windows 10. I guess the new module completely breaks this.
Date: Thu, 17 Dec 2020 14:01:23 +0000 [thread overview]
Message-ID: <bug-98300-4-jC9P0g0tBX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98300-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98300
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:
https://gcc.gnu.org/g:096164229a4c2d1efab9f259f50be1bdcdfc8abd
commit r11-6225-g096164229a4c2d1efab9f259f50be1bdcdfc8abd
Author: Nathan Sidwell <nathan@acm.org>
Date: Thu Dec 17 05:57:13 2020 -0800
bootstrap: Fix some windows issues [PR 98300]
When breaking out the sample server from the gcc/cp directory, it lost
its check for mmap, and the sample resolver just assumed it was there.
Fixed thusly. The non-mapping paths in module.cc weren't (recently)
excercised, and led to a signedness warning. Finally I'd missed
c++tools's config.h.in in the gcc_update script. There I took the
opportunity of adding a 'tools' segment of the dependency lists.
PR bootstrap/98300
contrib/
* gcc_update: Add c++tools/config.h.in.
c++tools/
* configure.ac: Check for sys/mman.h.
* resolver.cc: Don't assume mmap, O_CLOEXEC are available. Use
xmalloc.
* config.h.in: Regenerated.
* configure: Regenerated.
gcc/cp/
* module.cc: Fix ::read, ::write result signedness comparisons.
next prev parent reply other threads:[~2020-12-17 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 19:31 [Bug bootstrap/98300] New: " euloanty at live dot com
2020-12-15 19:37 ` [Bug bootstrap/98300] " euloanty at live dot com
2020-12-15 19:41 ` euloanty at live dot com
2020-12-15 19:42 ` nathan at gcc dot gnu.org
2020-12-15 19:43 ` euloanty at live dot com
2020-12-15 19:48 ` euloanty at live dot com
2020-12-15 20:14 ` nathan at gcc dot gnu.org
2020-12-15 20:17 ` euloanty at live dot com
2020-12-15 20:34 ` euloanty at live dot com
2020-12-15 23:02 ` euloanty at live dot com
2020-12-16 13:12 ` redi at gcc dot gnu.org
2020-12-16 21:50 ` nathan at gcc dot gnu.org
2020-12-17 14:01 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-04 14:04 ` nathan at gcc dot gnu.org
2021-01-04 15:23 ` rguenth at gcc dot gnu.org
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=bug-98300-4-jC9P0g0tBX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).