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] [12/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 19:34:29 +0000 [thread overview] Message-ID: <bug-108819-4-pzuMFMUWsp@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 ---------------------------------------------------------------------------- Target Milestone|13.0 |12.3 Status|UNCONFIRMED |NEW Summary|[13 Regression] ICE on |[12/13 Regression] ICE on |valid code at -O1 with |valid code at -O1 with |"-fno-tree-ccp |"-fno-tree-ccp |-fno-tree-forwprop" on |-fno-tree-forwprop" on |x86_64-linux-gnu: tree |x86_64-linux-gnu: tree |check: expected ssa_name, |check: expected ssa_name, |have integer_cst in |have integer_cst in |number_of_iterations_cltz, |number_of_iterations_cltz, |at |at |tree-ssa-loop-niter.cc:2394 |tree-ssa-loop-niter.cc:2394 Last reconfirmed| |2023-02-16 Known to work| |11.1.0, 11.3.0 Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- _7 = 1 & 1; That I think is wrong but I think the problem is before ivcanon and it was latent in GCC 12 even. reassoc1 produces: <bb 4> [local count: 114863530]: _20 = a.0_1 == 0; _21 = a.0_1 > 0; _7 = 1 & 1; if (_7 != 0) goto <bb 5>; [89.30%] else goto <bb 6>; [10.70%] From: <bb 4> [local count: 114863530]: _20 = a.0_1 == 0; _21 = a.0_1 > 0; _22 = _20 & _21; if (_22 != 0) goto <bb 5>; [89.30%] else goto <bb 6>; [10.70%] All it has: Optimizing range tests a.0_1 -[, 0] and +[, 0] and +[0, 0] into 0 GCC 11 looks ok though: From: a.0_1 = a; if (a.0_1 <= 0) goto <bb 4>; [20.45%] else goto <bb 6>; [79.55%] <bb 4> [local count: 114863530]: _20 = a.0_1 == 0; _21 = a.0_1 > 0; _22 = _20 & _21; if (_22 != 0) goto <bb 5>; [89.30%] else goto <bb 6>; [10.70%] to: a.0_1 = a; _20 = a.0_1 == 0; _16 = 0; _21 = a.0_1 > 0; _7 = 1 & _16; if (_7 != 0) goto <bb 4>; [89.30%] else goto <bb 5>; [10.70%] So I am going to declare this as a latent bug (which the verifiers don't catch either ...).
next prev parent reply other threads:[~2023-02-16 19:34 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 ` [Bug tree-optimization/108819] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-16 19:34 ` pinskia at gcc dot gnu.org [this message] 2023-02-17 7:59 ` [Bug tree-optimization/108819] [12/13 " 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-pzuMFMUWsp@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: linkBe 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).