public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113217] [14 Regression][aarch64] ICE in rtl_verify_bb_insns, at cfgrtl.cc:2796 since r14-6605-gc0911c6b357ba9
Date: Thu, 04 Jan 2024 10:36:05 +0000	[thread overview]
Message-ID: <bug-113217-4-bPYmKrKfjj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113217-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Alex Coplan <acoplan at gcc dot gnu.org> ---
Looks like the fix in r14-6784-gaca1f9d7cab3dc1a374a7dc0ec6f7a8d02d2869a wasn't
sufficient to prevent trying to move throwing accesses above debug insns.  ICEs
with just -O -fnon-call-exceptions -g.  I'll see what can be done about that. 
I don't think we need to punt on such opportunities.

  parent reply	other threads:[~2024-01-04 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 15:29 [Bug target/113217] New: " mjires at suse dot cz
2024-01-03 17:21 ` [Bug target/113217] " pinskia at gcc dot gnu.org
2024-01-03 17:23 ` acoplan at gcc dot gnu.org
2024-01-03 17:29 ` pinskia at gcc dot gnu.org
2024-01-03 17:29 ` pinskia at gcc dot gnu.org
2024-01-04 10:36 ` acoplan at gcc dot gnu.org [this message]
2024-01-04 15:54 ` pinskia at gcc dot gnu.org
2024-01-05 12:25 ` cvs-commit at gcc dot gnu.org
2024-01-05 12:27 ` acoplan 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-113217-4-bPYmKrKfjj@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).