public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106072] Bogus -Wnonnull warning breaks rust bootstrap Date: Tue, 15 Nov 2022 21:02:51 +0000 [thread overview] Message-ID: <bug-106072-4-GRLnvvTCTE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106072-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106072 --- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> --- At least when building the devel/rust/master branch as of 20221111, the warning doesn't occur any longer. I haven't investigated why, though.
next prev parent reply other threads:[~2022-11-15 21:02 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-24 8:00 [Bug c++/106072] New: " ro at gcc dot gnu.org 2022-06-28 12:56 ` [Bug c++/106072] " ro at gcc dot gnu.org 2022-06-28 12:56 ` ro at gcc dot gnu.org 2022-11-15 21:02 ` ro at gcc dot gnu.org [this message] 2022-12-13 17:24 ` ro at gcc dot gnu.org 2022-12-13 17:25 ` ro at gcc dot gnu.org 2022-12-13 17:35 ` [Bug c++/106072] [13 Regression] " pinskia at gcc dot gnu.org 2022-12-13 17:35 ` pinskia at gcc dot gnu.org 2022-12-13 17:37 ` pinskia at gcc dot gnu.org 2022-12-13 17:40 ` [Bug ipa/106072] " pinskia at gcc dot gnu.org 2022-12-13 17:46 ` pinskia at gcc dot gnu.org 2022-12-14 7:51 ` iains at gcc dot gnu.org 2022-12-14 8:04 ` iains at gcc dot gnu.org 2022-12-14 8:51 ` jakub at gcc dot gnu.org 2022-12-14 8:55 ` [Bug rust/106072] " jakub at gcc dot gnu.org 2022-12-14 10:17 ` [Bug rust/106072] [13 Regression] " tschwinge at gcc dot gnu.org 2022-12-14 10:36 ` cvs-commit at gcc dot gnu.org 2022-12-20 14:05 ` rguenth at gcc dot gnu.org 2022-12-20 14:06 ` ktkachov at gcc dot gnu.org 2022-12-20 14:08 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-106072-4-GRLnvvTCTE@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).