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/106091] [11/12/13 Regression] during RTL pass: swaps ICE: verify_flow_info failed: missing REG_EH_REGION note at the end of bb 69 with -fnon-call-exceptions
Date: Tue, 26 Jul 2022 02:31:15 +0000	[thread overview]
Message-ID: <bug-106091-4-xwIm42mohY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106091-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:f4286601933406142b46693660f7f4b682cb50a5

commit r13-1832-gf4286601933406142b46693660f7f4b682cb50a5
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Mon Jul 25 21:29:14 2022 -0500

    rs6000: Preserve REG_EH_REGION when replacing load/store [PR106091]

    As test case in PR106091 shows, rs6000 specific pass swaps
    doesn't preserve the reg_note REG_EH_REGION when replacing
    some load insn at the end of basic block, it causes the
    flow info verification to fail unexpectedly.  Since memory
    reference rtx may trap, this patch is to ensure we copy
    REG_EH_REGION reg_note while replacing swapped aligned load
    or store.

            PR target/106091

    gcc/ChangeLog:

            * config/rs6000/rs6000-p8swap.cc (replace_swapped_aligned_store):
Copy
            REG_EH_REGION when replacing one store insn having it.
            (replace_swapped_aligned_load): Likewise.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr106091.c: New test.

  parent reply	other threads:[~2022-07-26  2:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26 19:05 [Bug rtl-optimization/106091] New: " zsojka at seznam dot cz
2022-06-26 19:17 ` [Bug target/106091] " pinskia at gcc dot gnu.org
2022-06-27 10:46 ` rguenth at gcc dot gnu.org
2022-06-28 11:40 ` linkw at gcc dot gnu.org
2022-07-07  5:32 ` linkw at gcc dot gnu.org
2022-07-25 15:51 ` rguenth at gcc dot gnu.org
2022-07-25 16:37 ` segher at gcc dot gnu.org
2022-07-26  2:31 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-02  3:53 ` cvs-commit at gcc dot gnu.org
2022-08-02  3:56 ` cvs-commit at gcc dot gnu.org
2022-08-02  3:58 ` cvs-commit at gcc dot gnu.org
2022-08-02  4:06 ` linkw 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-106091-4-xwIm42mohY@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).