public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111435] [14 Regression] gimple_zero_one_valued_p() infinite recursion
Date: Mon, 18 Sep 2023 20:47:12 +0000 [thread overview]
Message-ID: <bug-111435-4-thKpf0394z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111435-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111435
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> s/recusive/recursive/
Thanks I committed it with the spelling fix applied.
next prev parent reply other threads:[~2023-09-18 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 19:54 [Bug tree-optimization/111435] New: " slyfox at gcc dot gnu.org
2023-09-16 19:55 ` [Bug tree-optimization/111435] " pinskia at gcc dot gnu.org
2023-09-16 19:59 ` pinskia at gcc dot gnu.org
2023-09-16 20:08 ` pinskia at gcc dot gnu.org
2023-09-16 21:37 ` slyfox at gcc dot gnu.org
2023-09-16 21:47 ` pinskia at gcc dot gnu.org
2023-09-16 21:54 ` pinskia at gcc dot gnu.org
2023-09-16 22:28 ` pinskia at gcc dot gnu.org
2023-09-17 1:45 ` pinskia at gcc dot gnu.org
2023-09-17 9:02 ` pinskia at gcc dot gnu.org
2023-09-17 10:50 ` slyfox at gcc dot gnu.org
2023-09-17 16:06 ` pinskia at gcc dot gnu.org
2023-09-18 8:33 ` jakub at gcc dot gnu.org
2023-09-18 20:45 ` cvs-commit at gcc dot gnu.org
2023-09-18 20:47 ` pinskia at gcc dot gnu.org [this message]
2023-09-19 0:15 ` pinskia at gcc dot gnu.org
2023-09-20 2:12 ` pinskia 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-111435-4-thKpf0394z@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).