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/106498] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a89866660945
Date: Tue, 02 Aug 2022 06:40:46 +0000	[thread overview]
Message-ID: <bug-106498-4-vFtiFED2PC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106498-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:c30bbd4d169c98b7535a30384c6a971ee875fa44

commit r13-1926-gc30bbd4d169c98b7535a30384c6a971ee875fa44
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Aug 2 08:37:16 2022 +0200

    tree-optimization/106498 - reduce SSA updates in autopar

    The following reduces the number of SSA updates done during autopar
    OMP expansion, specifically avoiding the cases that just add virtual
    operands (where maybe none have been before) in dead regions of the CFG.

    Instead virtual SSA update is delayed until after the pass.  There's
    much more TLC needed here, but test coverage makes it really difficult.

            PR tree-optimization/106498
            * omp-expand.cc (expand_omp_taskreg): Do not perform virtual
            SSA update here.
            (expand_omp_for): Or here.
            (execute_expand_omp): Instead schedule it here together
            with CFG cleanup via TODO.

  parent reply	other threads:[~2022-08-02  6:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 10:32 [Bug tree-optimization/106498] New: [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 asolokha at gmx dot com
2022-08-01 11:17 ` [Bug tree-optimization/106498] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a89866660945 marxin at gcc dot gnu.org
2022-08-01 13:22 ` rguenth at gcc dot gnu.org
2022-08-01 13:57 ` rguenth at gcc dot gnu.org
2022-08-02  6:40 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-02  6:41 ` rguenth 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-106498-4-vFtiFED2PC@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).