public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111043] [14 regression] ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1068
Date: Sun, 17 Sep 2023 17:11:32 +0000	[thread overview]
Message-ID: <bug-111043-4-PI349gMhxz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111043-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
A third reproducer, with -O3 required:

long g_18;
int g_170, g_759, g_1114;
extern void safe_lshift_func_uint64_t_u_u();
void func_35() {
  int __trans_tmp_1;
  for (; g_759 >= 0; g_759 = g_759 - (long)7) {
    g_170 = 0;
    if (__trans_tmp_1)
      return;
    if (g_1114)
      safe_lshift_func_uint64_t_u_u();
  }
}
void func_20() {
  int __trans_tmp_2;
  g_18 = 7;
  for (; g_18 >= 0; g_18 -= 1)
    __attribute__(()) int right = g_18;
  __trans_tmp_2 = right < 0 || right >= 2 ?: right;
  if (__trans_tmp_2)
    for (;;)
      ;
  func_35();
}

  parent reply	other threads:[~2023-09-17 17:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 20:39 [Bug c/111043] New: " shaohua.li at inf dot ethz.ch
2023-08-16 20:43 ` [Bug tree-optimization/111043] [14 regression] " pinskia at gcc dot gnu.org
2023-08-17 10:46 ` dcb314 at hotmail dot com
2023-08-18  8:10 ` dcb314 at hotmail dot com
2023-08-18  8:27 ` dcb314 at hotmail dot com
2023-08-18  8:38 ` dcb314 at hotmail dot com
2023-08-20  7:51 ` pinskia at gcc dot gnu.org
2023-09-03 10:06 ` zhendong.su at inf dot ethz.ch
2023-09-17 17:11 ` dcb314 at hotmail dot com [this message]
2023-10-17 12:25 ` rguenth at gcc dot gnu.org
2023-11-01  7:32 ` zhendong.su at inf dot ethz.ch
2024-01-11 13:52 ` [Bug tree-optimization/111043] [14 regression] ICE in adjust_loop_info_after_peeling, at tree-ssa-loop-ivcanon.cc:1068 since r14-2675-gef28aadad6e5cf 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-111043-4-PI349gMhxz@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).