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 tree-optimization/113237] [14 Regression] ICE verify_ssa failed when building 500.perlbench_r since r14-6822-g01f4251b8775c8
Date: Fri, 12 Jan 2024 15:32:45 +0000	[thread overview]
Message-ID: <bug-113237-4-SWy59hQoZ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113237-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>:

https://gcc.gnu.org/g:99c0a540d6689ede068f9ba98af6f38c3cd71362

commit r14-7196-g99c0a540d6689ede068f9ba98af6f38c3cd71362
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Fri Jan 12 15:25:58 2024 +0000

    middle-end: thread through existing LCSSA variable for alternative exits
too [PR113237]

    Builing on top of the previous patch, similar to when we have a single exit
if
    we have a case where all exits are considered early exits and there are
existing
    non virtual phi then in order to maintain LCSSA we have to use the existing
PHI
    variables.  We can't simply clear them and just rebuild them because the
order
    of the PHIs in the main exit must match the original exit for when we add
the
    skip_epilog guard.

    But the infrastructure is already in place to maintain them, we just have
to use
    the right value.

    gcc/ChangeLog:

            PR tree-optimization/113237
            * tree-vect-loop-manip.cc (slpeel_tree_duplicate_loop_to_edge_cfg):
Use
            existing LCSSA variable for exit when all exits are early break.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/113237
            * gcc.dg/vect/vect-early-break_98-pr113237.c: New test.

  parent reply	other threads:[~2024-01-12 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 17:49 [Bug tree-optimization/113237] New: " jamborm at gcc dot gnu.org
2024-01-04 17:52 ` [Bug tree-optimization/113237] " pinskia at gcc dot gnu.org
2024-01-04 18:00 ` tnfchris at gcc dot gnu.org
2024-01-04 18:02 ` tnfchris at gcc dot gnu.org
2024-01-04 18:48 ` tnfchris at gcc dot gnu.org
2024-01-07 17:27 ` tnfchris at gcc dot gnu.org
2024-01-12 15:32 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-12 15:36 ` tnfchris 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-113237-4-SWy59hQoZ7@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).