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 target/107209] [13 Regression] ICE: verify_gimple failed (error: statement marked for throw, but doesn't)
Date: Wed, 30 Nov 2022 17:26:22 +0000	[thread overview]
Message-ID: <bug-107209-4-9w94QMaEkL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107209-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |ktkachov at gcc dot gnu.org,
                   |                            |rearnsha at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Looking at other backends, rs6000 uses in *gimple_fold_builtin gsi_replace
(..., true);
all the time, ix86 gsi_replace (..., false); all the time, alpha with true,
aarch64 with true.  But perhaps what is more important if the builtins folded
are declared nothrow or not, if they are nothrow, then they shouldn't have any
EH edges at the start already and so it shouldn't matter what is used.

  parent reply	other threads:[~2022-11-30 17:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  4:29 [Bug tree-optimization/107209] New: " asolokha at gmx dot com
2022-10-11  7:27 ` [Bug tree-optimization/107209] " rguenth at gcc dot gnu.org
2022-10-11 15:57 ` pinskia at gcc dot gnu.org
2022-10-18  8:08 ` rguenth at gcc dot gnu.org
2022-10-18  8:29 ` [Bug target/107209] " rguenth at gcc dot gnu.org
2022-11-30 17:26 ` jakub at gcc dot gnu.org [this message]
2022-12-20  9:22 ` ktkachov at gcc dot gnu.org
2022-12-20  9:29 ` jakub at gcc dot gnu.org
2023-01-13 10:01 ` cvs-commit at gcc dot gnu.org
2023-01-13 10:09 ` rsandifo 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-107209-4-9w94QMaEkL@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).