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 target/113093] [14 Regression][aarch64] ICE in rtl_verify_bb_insn, at cfgrtl.cc:2796 since r14-6605-gc0911c6b357ba9 Date: Thu, 21 Dec 2023 10:53:28 +0000 [thread overview] Message-ID: <bug-113093-4-KycnbrYdy4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113093-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113093 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alex Coplan <acoplan@gcc.gnu.org>: https://gcc.gnu.org/g:aca1f9d7cab3dc1a374a7dc0ec6f7a8d02d2869a commit r14-6784-gaca1f9d7cab3dc1a374a7dc0ec6f7a8d02d2869a Author: Alex Coplan <alex.coplan@arm.com> Date: Thu Dec 21 10:52:44 2023 +0000 aarch64: Prevent moving throwing accesses in ldp/stp pass [PR113093] As the PR shows, there was nothing to prevent the ldp/stp pass from trying to move throwing insns, which lead to an RTL verification failure. This patch fixes that. gcc/ChangeLog: PR target/113093 * config/aarch64/aarch64-ldp-fusion.cc (latest_hazard_before): If the insn is throwing, record the previous insn as a hazard to prevent moving it from the end of the BB. gcc/testsuite/ChangeLog: PR target/113093 * gcc.dg/pr113093.c: New test.
next prev parent reply other threads:[~2023-12-21 10:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-20 13:10 [Bug target/113093] New: " mjires at suse dot cz 2023-12-20 13:21 ` [Bug target/113093] " rguenth at gcc dot gnu.org 2023-12-20 14:36 ` acoplan at gcc dot gnu.org 2023-12-20 15:34 ` acoplan at gcc dot gnu.org 2023-12-21 10:53 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-21 10:55 ` 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-113093-4-KycnbrYdy4@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).