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/114792] [14 Regression] ICE on valid code at -O1 with "-fno-tree-ccp -fno-tree-copy-prop" on x86_64-linux-gnu: in get_loop_body, at cfgloop.cc:903
Date: Thu, 25 Apr 2024 06:14:52 +0000	[thread overview]
Message-ID: <bug-114792-4-v2vwCcWqHd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114792-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #58024|0                           |1
        is obsolete|                            |

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 58033
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58033&action=edit
patch

I'm now testing this which is more minimal surgery at least making sure we
process loops in similar order as unrolling does.  I'm not 100% convinced this
is enough but it restores part of the consistency (unroll also doesn't unloop
an outer loop before cleaning up the CFG and rebuilding loops after unlooping
an inner loop).

  parent reply	other threads:[~2024-04-25  6:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 11:39 [Bug tree-optimization/114792] New: " zhendong.su at inf dot ethz.ch
2024-04-21 15:33 ` [Bug tree-optimization/114792] " hjl.tools at gmail dot com
2024-04-21 20:25 ` [Bug tree-optimization/114792] [14 Regression] " pinskia at gcc dot gnu.org
2024-04-21 20:26 ` pinskia at gcc dot gnu.org
2024-04-22  7:17 ` jakub at gcc dot gnu.org
2024-04-24 13:04 ` rguenth at gcc dot gnu.org
2024-04-24 13:05 ` rguenth at gcc dot gnu.org
2024-04-25  5:45 ` rguenth at gcc dot gnu.org
2024-04-25  6:13 ` rguenth at gcc dot gnu.org
2024-04-25  6:14 ` rguenth at gcc dot gnu.org [this message]
2024-04-25 13:20 ` cvs-commit at gcc dot gnu.org
2024-04-25 13:21 ` 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-114792-4-v2vwCcWqHd@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).