public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113707] [14 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r14-8683
Date: Thu, 01 Feb 2024 17:40:40 +0000	[thread overview]
Message-ID: <bug-113707-4-QeivET5ajz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113707-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Zhendong Su <zhendong.su at inf dot ethz.ch> ---
Another related test for -O3 (only):

[555] % gcctk -O3 small.c
during GIMPLE pass: cunroll
small.c: In function ‘main’:
small.c:14:5: internal compiler error: Segmentation fault
   14 | int main() {
      |     ^~~~
0x1161623 crash_signal
        ../../gcc-trunk/gcc/toplev.cc:317
0x7fa97fd5308f ???
       
/build/glibc-wuryBv/glibc-2.31/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0xda0c28 extract_ops_from_tree(tree_node*, tree_code*, tree_node**,
tree_node**, tree_node**)
        ../../gcc-trunk/gcc/gimple-expr.cc:530
0xd980e0 gimple_build_assign(tree_node*, tree_node*)
        ../../gcc-trunk/gcc/gimple.cc:454
0x137c91c eliminate_dom_walker::eliminate_cleanup(bool)
        ../../gcc-trunk/gcc/tree-ssa-sccvn.cc:7494
0x13917db do_rpo_vn_1
        ../../gcc-trunk/gcc/tree-ssa-sccvn.cc:8720
0x13923b3 do_rpo_vn(function*, edge_def*, bitmap_head*, bool, bool, bool,
vn_lookup_kind)
        ../../gcc-trunk/gcc/tree-ssa-sccvn.cc:8749
0x12df179 tree_unroll_loops_completely
        ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:1554
0x12df2b3 execute
        ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:1673
0x12df2b3 execute
        ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:1663
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
[556] %
[556] % cat small.c
int a, b, c, d, e, f, g, h, j, k, l;
void n() {
  while (c)
    if (1) {
      for (h = 5; h; h--) {
        int m = e % 2;
        d = ~g || h ^ m / -1;
        if (h > 5)
          e = k;
      }
      return;
    }
}
int main() {
  if (a)
    for (int i = 0; i < 2; i++) {
      for (f = 1; f < 6; f++)
        for (c = 7; c >= 0; c--)
          if (l)
            b = 0;
      n();
    }
  return 0;
}

  parent reply	other threads:[~2024-02-01 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 15:58 [Bug tree-optimization/113707] New: ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault zhendong.su at inf dot ethz.ch
2024-02-01 16:10 ` [Bug tree-optimization/113707] [14 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r14-8683 jakub at gcc dot gnu.org
2024-02-01 17:40 ` zhendong.su at inf dot ethz.ch [this message]
2024-02-05  8:24 ` rguenth at gcc dot gnu.org
2024-02-05  8:44 ` rguenth at gcc dot gnu.org
2024-02-05  8:51 ` rguenth at gcc dot gnu.org
2024-02-05 10:07 ` cvs-commit at gcc dot gnu.org
2024-02-05 10:08 ` 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-113707-4-QeivET5ajz@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).