From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/106072] [13 Regression] -Wnonnull warning breaks rust bootstrap
Date: Wed, 14 Dec 2022 10:17:41 +0000 [thread overview]
Message-ID: <bug-106072-35322-sF3L8qV6Dh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106072-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106072
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://github.com/Rust-GCC
| |/gccrs/pull/1619
CC| |tschwinge at gcc dot gnu.org
Blocks|95507 |
Summary|[13 Regression] Bogus |[13 Regression] -Wnonnull
|-Wnonnull warning breaks |warning breaks rust
|rust bootstrap |bootstrap
Keywords|diagnostic |
--- Comment #15 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Thanks, Jakub!
So, an actual GCC/Rust issue, not PR95507 "(Wnonnull) - [meta-bug]
bogus/missing -Wnonnull".
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95507
[Bug 95507] [meta-bug] bogus/missing -Wnonnull
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-14 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106072-35322@http.gcc.gnu.org/bugzilla/>
2022-12-14 8:51 ` [Bug rust/106072] [13 Regression] Bogus " jakub at gcc dot gnu.org
2022-12-14 8:55 ` jakub at gcc dot gnu.org
2022-12-14 10:06 ` tschwinge at gcc dot gnu.org
2022-12-14 10:17 ` tschwinge at gcc dot gnu.org [this message]
2022-12-14 10:36 ` [Bug rust/106072] [13 Regression] " 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-35322-sF3L8qV6Dh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@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).