public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100086] [11 Regression] spurious -Wnonnull with __builtin_expect
Date: Mon, 31 Jan 2022 14:52:38 +0000 [thread overview]
Message-ID: <bug-100086-4-sMqYf6sxiV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100086-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100086
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
CC| |marxin at gcc dot gnu.org
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> The testcase no longer reproduces the issue with GCC 12 for me, GCC 11 still
> does. I wonder what fixed it.
Fixed with r12-1546-g786188e8b8cab47c.
next prev parent reply other threads:[~2022-01-31 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 20:28 [Bug tree-optimization/100086] New: " msebor at gcc dot gnu.org
2021-04-14 20:32 ` [Bug tree-optimization/100086] [11 Regression] " msebor at gcc dot gnu.org
2021-04-15 7:00 ` rguenth at gcc dot gnu.org
2021-04-27 11:40 ` [Bug tree-optimization/100086] [11/12 " jakub at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2022-01-21 12:37 ` [Bug tree-optimization/100086] [11 " rguenth at gcc dot gnu.org
2022-01-31 14:52 ` marxin at gcc dot gnu.org [this message]
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2023-05-29 10:04 ` jakub 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-100086-4-sMqYf6sxiV@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).