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 middle-end/110874] [14 Regression] ice with -O2 with recent gcc Date: Fri, 04 Aug 2023 07:27:01 +0000 [thread overview] Message-ID: <bug-110874-4-QDkOByzEQJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110874-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110874 --- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:91c963ea6f845a0c59b7523a5330b8d3ed1beb6a commit r14-2978-g91c963ea6f845a0c59b7523a5330b8d3ed1beb6a Author: Andrew Pinski <apinski@marvell.com> Date: Wed Aug 2 14:49:00 2023 -0700 Fix PR 110874: infinite loop in gimple_bitwise_inverted_equal_p with fre This changes gimple_bitwise_inverted_equal_p to use a 2 different match patterns to try to match bit_not wrapped with a possible nop_convert and a comparison also wrapped with a possible nop_convert. This is to avoid being recursive. OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions. gcc/ChangeLog: PR tree-optimization/110874 * gimple-match-head.cc (gimple_bit_not_with_nop): New declaration. (gimple_maybe_cmp): Likewise. (gimple_bitwise_inverted_equal_p): Rewrite to use gimple_bit_not_with_nop and gimple_maybe_cmp instead of being recursive. * match.pd (bit_not_with_nop): New match pattern. (maybe_cmp): Likewise. gcc/testsuite/ChangeLog: PR tree-optimization/110874 * gcc.c-torture/compile/pr110874-a.c: New test.
next prev parent reply other threads:[~2023-08-04 7:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-02 13:46 [Bug c/110874] New: " dcb314 at hotmail dot com 2023-08-02 15:23 ` [Bug c/110874] " dcb314 at hotmail dot com 2023-08-02 15:58 ` [Bug middle-end/110874] [14 Regression] " pinskia at gcc dot gnu.org 2023-08-02 16:12 ` pinskia at gcc dot gnu.org 2023-08-02 16:59 ` pinskia at gcc dot gnu.org 2023-08-02 20:11 ` dcb314 at hotmail dot com 2023-08-02 20:14 ` dcb314 at hotmail dot com 2023-08-02 20:17 ` pinskia at gcc dot gnu.org 2023-08-02 20:32 ` pinskia at gcc dot gnu.org 2023-08-02 21:01 ` pinskia at gcc dot gnu.org 2023-08-02 21:09 ` pinskia at gcc dot gnu.org 2023-08-03 2:44 ` pinskia at gcc dot gnu.org 2023-08-03 6:59 ` pinskia at gcc dot gnu.org 2023-08-03 7:18 ` pinskia at gcc dot gnu.org 2023-08-03 22:49 ` pinskia at gcc dot gnu.org 2023-08-04 7:27 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-04 7:27 ` 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-110874-4-QDkOByzEQJ@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).