public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108825] [13 Regression] error during GIMPLE pass: unrolljam
Date: Mon, 20 Feb 2023 08:53:27 +0000	[thread overview]
Message-ID: <bug-108825-4-RbM5N5DStM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108825-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|needs-bisection             |

--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is that unroll-and-jam applies RPO VN on the transformed body but
that leaves the IL in "indetermined" state (it returns a TODO to make it valid
again).  But unroll-and-jam then continues to transform another loop and
in using the tree_unroll_loop helper runs into tree_transform_and_unroll_loop
performing IL checking

  checking_verify_flow_info ();
  checking_verify_loop_structure ();
  checking_verify_loop_closed_ssa (true, loop);
  if (new_loop)
    checking_verify_loop_closed_ssa (true, new_loop);

in particular the loop-specific LC SSA verifiers run function-wide SSA
verification.

In generally IL verification in these kind of helpers is frowned upon since
it easily results in quadraticness when checking is enabled.

I'm "fixing" the loop-local LC SSA verifier to not perform function-wide
SSA verification but the real fix would be to delete all of the above
(and rely on after-pass IL verification).

  parent reply	other threads:[~2023-02-20  8:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 17:34 [Bug c/108825] New: " dcb314 at hotmail dot com
2023-02-16 17:50 ` [Bug tree-optimization/108825] [13 Regression] " pinskia at gcc dot gnu.org
2023-02-16 18:37 ` dcb314 at hotmail dot com
2023-02-16 18:54 ` dcb314 at hotmail dot com
2023-02-16 19:43 ` dcb314 at hotmail dot com
2023-02-16 20:10 ` dcb314 at hotmail dot com
2023-02-16 20:44 ` dcb314 at hotmail dot com
2023-02-16 20:48 ` pinskia at gcc dot gnu.org
2023-02-16 21:01 ` dcb314 at hotmail dot com
2023-02-16 21:40 ` dcb314 at hotmail dot com
2023-02-17  8:01 ` rguenth at gcc dot gnu.org
2023-02-20  8:53 ` rguenth at gcc dot gnu.org [this message]
2023-02-20 10:04 ` cvs-commit at gcc dot gnu.org
2023-02-20 10:32 ` 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-108825-4-RbM5N5DStM@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).