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/106249] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a898666609452e
Date: Wed, 13 Jul 2022 07:36:09 +0000	[thread overview]
Message-ID: <bug-106249-4-gSGN6EBP2c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106249-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:c479c40f8c8fee0fb70e8a365b61c55739f448e1

commit r13-1653-gc479c40f8c8fee0fb70e8a365b61c55739f448e1
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jul 13 08:27:57 2022 +0200

    tree-optimization/106249 - unroll-and-jam and LC SSA upate

    When I delayed the LC SSA update in unroll-and-jam this exposed
    an issue that tree_transform_and_unroll_loop does a full function
    LC SSA verification when new_loop is NULL (when it doesn't need to
    do versioning).  That wasn't intended.  I also took the chance
    to make the versioning in tree_transform_and_unroll_loop use
    TODO_update_ssa_nophi for the loop versioning SSA update which
    I somehow missed earlier.

            PR tree-optimization/106249
            * tree-ssa-loop-manip.cc (tree_transform_and_unroll_loop):
            Only verify LC SSA of the new_loop if we created it.
            Use TODO_update_ssa_nophi for the SSA update after versioning
            the loop.

            * gcc.dg/pr106249.c: New testcase.

  parent reply	other threads:[~2022-07-13  7:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  5:05 [Bug tree-optimization/106249] New: ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 asolokha at gmx dot com
2022-07-11  5:32 ` [Bug tree-optimization/106249] [13 Regression] " pinskia at gcc dot gnu.org
2022-07-11  7:38 ` rguenth at gcc dot gnu.org
2022-07-11  7:39 ` rguenth at gcc dot gnu.org
2022-07-11  7:41 ` rguenth at gcc dot gnu.org
2022-07-12 16:10 ` asolokha at gmx dot com
2022-07-13  7:15 ` [Bug tree-optimization/106249] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a898666609452e marxin at gcc dot gnu.org
2022-07-13  7:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-13  7:36 ` rguenth at gcc dot gnu.org
2022-07-14 17:26 ` pinskia at gcc dot gnu.org
2022-07-26  9:27 ` jakub at gcc dot gnu.org
2022-12-20 14:35 ` rguenth at gcc dot gnu.org
2023-02-08 11:45 ` asolokha at gmx dot com
2023-02-10 10:17 ` 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-106249-4-gSGN6EBP2c@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).