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 rtl-optimization/106751] [10 Regression] internal compiler error: in purge_dead_edges with inline-asm goto
Date: Wed, 03 May 2023 15:20:01 +0000	[thread overview]
Message-ID: <bug-106751-4-y7JfzjTLux@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106751-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

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

commit r10-11348-gc88f917d2aa1c2ac065fbc0a10298f5551f392b6
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Dec 16 10:19:22 2022 +0100

    loop-invariant: Split preheader edge if the preheader bb ends with jump
[PR106751]

    The RTL loop passes only request simple preheaders, but don't require
    fallthru preheaders, while move_invariant_reg apparently assumes the
    latter, that it can just append instruction(s) to the end of the preheader
    basic block.

    The following patch fixes that by splitting the preheader edge if
    the preheader bb ends with a JUMP_INSN (asm goto in this case).
    Without that we get control flow in the middle of a bb.

    2022-12-16  Jakub Jelinek  <jakub@redhat.com>

            PR rtl-optimization/106751
            * loop-invariant.c (move_invariant_reg): If preheader bb ends
            with a JUMP_INSN, split the preheader edge and emit invariants
            into the new preheader basic block.

            * gcc.c-torture/compile/pr106751.c: New test.

    (cherry picked from commit ddcaa60983b50378bde1b7e327086fe0ce101795)

  parent reply	other threads:[~2023-05-03 15:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 10:09 [Bug c/106751] New: internal compiler error: in purge_dead_edges, at cfgrtl.cc:3347 christophe.leroy at csgroup dot eu
2022-08-26 10:10 ` [Bug c/106751] " christophe.leroy at csgroup dot eu
2022-08-26 12:20 ` [Bug target/106751] " christophe.leroy at csgroup dot eu
2022-08-26 12:38 ` marxin at gcc dot gnu.org
2022-08-26 18:07 ` [Bug middle-end/106751] internal compiler error: in purge_dead_edges with inline-asm goto pinskia at gcc dot gnu.org
2022-08-26 18:08 ` pinskia at gcc dot gnu.org
2022-08-26 18:14 ` [Bug rtl-optimization/106751] " pinskia at gcc dot gnu.org
2022-08-26 18:21 ` pinskia at gcc dot gnu.org
2022-09-13 15:50 ` segher at gcc dot gnu.org
2022-12-15 13:10 ` [Bug rtl-optimization/106751] [10/11/12/13 Regression] " jakub at gcc dot gnu.org
2022-12-15 15:51 ` jakub at gcc dot gnu.org
2022-12-15 16:53 ` jakub at gcc dot gnu.org
2022-12-15 18:05 ` rguenth at gcc dot gnu.org
2022-12-16  9:20 ` cvs-commit at gcc dot gnu.org
2022-12-16  9:23 ` [Bug rtl-optimization/106751] [10/11/12 " jakub at gcc dot gnu.org
2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:56 ` [Bug rtl-optimization/106751] [10/11 " jakub at gcc dot gnu.org
2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org
2023-05-03  9:26 ` [Bug rtl-optimization/106751] [10 " jakub at gcc dot gnu.org
2023-05-03 15:20 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-04  7:19 ` jakub 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-106751-4-y7JfzjTLux@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).