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/101372] [12 Regression] Bootstrap failure compiling gcc/cp/module.cc Date: Thu, 08 Jul 2021 22:40:59 +0000 [thread overview] Message-ID: <bug-101372-4-heBTqncgBU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101372-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101372 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>: https://gcc.gnu.org/g:79d3378c7d73814442eb468c562ab8aa572f9c43 commit r12-2178-g79d3378c7d73814442eb468c562ab8aa572f9c43 Author: Martin Sebor <msebor@redhat.com> Date: Thu Jul 8 16:36:15 2021 -0600 Move warning suppression to the ultimate callee. Resolves: PR bootstrap/101372 - -Warray-bounds in gcc/cp/module.cc causing bootstrap failure gcc/cp/ChangeLog: PR bootstrap/101372 * module.cc (identifier): Suppress warning. (module_state::read_macro_maps): Remove warning suppression. (module_state::install_macros): Ditto.
next prev parent reply other threads:[~2021-07-08 22:40 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-08 6:53 [Bug bootstrap/101372] New: " tnfchris at gcc dot gnu.org 2021-07-08 7:42 ` [Bug bootstrap/101372] " rguenth at gcc dot gnu.org 2021-07-08 7:50 ` rguenth at gcc dot gnu.org 2021-07-08 9:30 ` tnfchris at gcc dot gnu.org 2021-07-08 10:46 ` schwab@linux-m68k.org 2021-07-08 19:11 ` msebor at gcc dot gnu.org 2021-07-08 22:35 ` segher at gcc dot gnu.org 2021-07-08 22:40 ` cvs-commit at gcc dot gnu.org [this message] 2021-07-08 22:42 ` [Bug bootstrap/101372] [12 Regression] -Warray-bounds in gcc/cp/module.cc causing bootstrap failure msebor 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-101372-4-heBTqncgBU@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: 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).