public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108819] [13 Regression] ICE on valid code at -O1 with "-fno-tree-ccp -fno-tree-forwprop" on x86_64-linux-gnu: tree check: expected ssa_name, have integer_cst in number_of_iterations_cltz, at tree-ssa-loop-niter.cc:2394
Date: Thu, 16 Feb 2023 15:39:55 +0000	[thread overview]
Message-ID: <bug-108819-4-czjz6HHoPZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108819-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
   Target Milestone|---                         |13.0
            Summary|ICE on valid code at -O1    |[13 Regression] ICE on
                   |with "-fno-tree-ccp         |valid code at -O1 with
                   |-fno-tree-forwprop" on      |"-fno-tree-ccp
                   |x86_64-linux-gnu: tree      |-fno-tree-forwprop" on
                   |check: expected ssa_name,   |x86_64-linux-gnu: tree
                   |have integer_cst in         |check: expected ssa_name,
                   |number_of_iterations_cltz,  |have integer_cst in
                   |at                          |number_of_iterations_cltz,
                   |tree-ssa-loop-niter.cc:2394 |at
                   |                            |tree-ssa-loop-niter.cc:2394
            Version|unknown                     |13.0

  reply	other threads:[~2023-02-16 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 10:35 [Bug tree-optimization/108819] New: " zhendong.su at inf dot ethz.ch
2023-02-16 15:39 ` pinskia at gcc dot gnu.org [this message]
2023-02-16 19:34 ` [Bug tree-optimization/108819] [12/13 Regression] " pinskia at gcc dot gnu.org
2023-02-17  7:59 ` rguenth at gcc dot gnu.org
2023-02-17 13:20 ` rguenth at gcc dot gnu.org
2023-02-17 16:46 ` jakub at gcc dot gnu.org
2023-02-18 11:41 ` cvs-commit at gcc dot gnu.org
2023-02-18 11:42 ` [Bug tree-optimization/108819] [12 " jakub at gcc dot gnu.org
2023-02-20  7:44 ` cvs-commit at gcc dot gnu.org
2023-03-19  5:29 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:26 ` jakub 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-108819-4-czjz6HHoPZ@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).