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: Tue, 20 Dec 2022 09:29:31 +0000	[thread overview]
Message-ID: <bug-107209-4-ciPgsgfJnr@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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to ktkachov from comment #5)
> aarch64_could_trap_p returns true for it as it can raise an FP exception.
> Should that affect the nothrow attribute though? Shouldn't that be for C++
> exceptions only?

nothrow isn't just C++ attribute, it is also for C, which uses EH e.g. for
pthread_cancel or the non-call exceptions if -fexceptions.  Here
-fnon-call-exceptions is on and the builtin can trap, so it is right that the
builtin isn't marked nothrow,
but then you need to either punt on folding that on GIMPLE if
flag_non_call_exceptions
and there is an EH edge for it, or ensure somehow the EH stuff is preserved
during the folding.

  parent reply	other threads:[~2022-12-20  9:29 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
2022-12-20  9:22 ` ktkachov at gcc dot gnu.org
2022-12-20  9:29 ` jakub at gcc dot gnu.org [this message]
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-ciPgsgfJnr@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).