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/107153] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645
Date: Fri, 07 Oct 2022 12:27:55 +0000	[thread overview]
Message-ID: <bug-107153-4-kCubZEdf54@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107153-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:89228e3985c5cdf6be58a3b5b1afcad91e9e3422

commit r13-3161-g89228e3985c5cdf6be58a3b5b1afcad91e9e3422
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Oct 7 10:28:56 2022 +0200

    tree-optimization/107153 - autopar SSA update issue

    autopar performs insertion of stores, eventually requiring a
    virtual loop PHI and assorted LC PHI adjustments which we intend
    to do once after the pass finishes.  But we also perform intermediate
    update_ssa after loop duplication which can lose this fact.  The
    following forces renaming of the virtual operand before the final
    SSA update to fix that.  It also removes the explicit update_ssa
    call from the gimple_duplicate_sese_tail utility as has been done
    for all other such utilities and instead performs the SSA update
    from autopar.

            PR tree-optimization/107153
            * tree-cfg.cc (gimple_duplicate_sese_tail): Do not update
            SSA form here.
            * tree-parloops.cc (gen_parallel_loop): Update SSA form
            after to-exit-first transform, no PHI insertion is necessary.
            (pass_parallelize_loops::execute): Force re-write of the
            virtual operand SSA web.

            * gcc.dg/autopar/pr107153.c: New testcase.

  parent reply	other threads:[~2022-10-07 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 13:04 [Bug tree-optimization/107153] New: " asolokha at gmx dot com
2022-10-04 13:12 ` [Bug tree-optimization/107153] " marxin at gcc dot gnu.org
2022-10-06 10:13 ` rguenth at gcc dot gnu.org
2022-10-07  8:29 ` rguenth at gcc dot gnu.org
2022-10-07 12:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-07 12:28 ` rguenth at gcc dot gnu.org
2022-10-10 10:05 ` cvs-commit 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-107153-4-kCubZEdf54@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).