public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110271] [14 Regression] UICE on pycryptodome-3.17.0 during GIMPLE pass: widening_mul: in gsi_replace, at gimple-iterator.cc:437
Date: Thu, 15 Jun 2023 20:52:57 +0000	[thread overview]
Message-ID: <bug-110271-4-DXWE6BNCHG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110271-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110271

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The problem is that I thought match_arith_overflow returns true if it replaced
something, but that is not the case, it only returns true for the BIT_NOT_EXPR
case when it removed the stmt.
So, I think the right test for whether match_arith_overflow actually replaced
something is whether gsi_stmt (gsi) == stmt.

  parent reply	other threads:[~2023-06-15 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 18:09 [Bug middle-end/110271] New: " slyfox at gcc dot gnu.org
2023-06-15 18:11 ` [Bug middle-end/110271] " slyfox at gcc dot gnu.org
2023-06-15 19:17 ` [Bug tree-optimization/110271] " pinskia at gcc dot gnu.org
2023-06-15 19:19 ` pinskia at gcc dot gnu.org
2023-06-15 19:34 ` pinskia at gcc dot gnu.org
2023-06-15 20:52 ` jakub at gcc dot gnu.org [this message]
2023-06-16 17:48 ` cvs-commit at gcc dot gnu.org
2023-06-16 18:02 ` jakub at gcc dot gnu.org
2023-06-16 20:43 ` slyfox at gcc dot gnu.org
2023-06-17  8:34 ` 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-110271-4-DXWE6BNCHG@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).