public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103231] ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault Date: Sun, 14 Nov 2021 10:54:01 +0000 [thread overview] Message-ID: <bug-103231-4-XloEp9pzPa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103231-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103231 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marxin at gcc dot gnu.org Last reconfirmed| |2021-11-14 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- I can reproduce it with ulimit -s 4096, having ulimit -s 8192 works. BT is following: #0 gimple_ranger::range_of_stmt (this=0x2ceda20, r=..., s=0x7ffff72e9800, name=0x7ffff72ea1b0) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:259 #1 0x0000000001bc1045 in gimple_ranger::range_on_entry (this=0x2ceda20, r=..., bb=0x7ffff766db60, name=0x7ffff72ea1b0) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:141 #2 0x0000000001bc1b91 in gimple_ranger::range_of_expr (this=0x2ceda20, r=..., expr=0x7ffff72ea1b0, stmt=<optimized out>) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:118 #3 0x0000000001bc128c in gimple_ranger::range_on_exit (this=0x2ceda20, r=..., bb=0x7ffff766db60, name=0x7ffff72ea1b0) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:178 #4 0x0000000001bc1eee in gimple_ranger::range_on_edge (this=0x2ceda20, r=..., e=<optimized out>, name=0x7ffff72ea1b0) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:222 #5 0x0000000001bc8818 in fur_stmt::get_phi_operand (this=<optimized out>, r=..., expr=0x7ffff72ea1b0, e=0x7ffff77802d0) at /home/marxin/Programming/gcc/gcc/gimple-range-fold.cc:167 #6 0x0000000001bca5cf in fold_using_range::range_of_phi (this=0x7fffffc034ef, r=..., phi=0x7ffff72e9a00, src=...) at /home/marxin/Programming/gcc/gcc/gimple-range-fold.cc:789 #7 0x0000000001bccea1 in fold_using_range::fold_stmt (this=0x7fffffc034ef, r=..., s=0x7ffff72e9a00, src=..., name=0x7ffff72ea240) at /home/marxin/Programming/gcc/gcc/gimple-range-fold.cc:554 #8 0x0000000001bc1457 in gimple_ranger::fold_range_internal (this=this@entry=0x2ceda20, r=..., s=s@entry=0x7ffff72e9a00, name=name@entry=0x7ffff72ea240) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:243 #9 0x0000000001bc1707 in gimple_ranger::range_of_stmt (this=0x2ceda20, r=..., s=0x7ffff72e9a00, name=0x7ffff72ea240) at /home/marxin/Programming/gcc/gcc/gimple-range.cc:296
next prev parent reply other threads:[~2021-11-14 10:54 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-14 10:31 [Bug tree-optimization/103231] New: " zhendong.su at inf dot ethz.ch 2021-11-14 10:34 ` Jan Hubicka 2021-11-14 10:34 ` [Bug tree-optimization/103231] " hubicka at kam dot mff.cuni.cz 2021-11-14 10:37 ` pinskia at gcc dot gnu.org 2021-11-14 10:54 ` marxin at gcc dot gnu.org [this message] 2021-11-14 10:55 ` [Bug tree-optimization/103231] [12 Regression] ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r12-5014-g6b8b959675a3e14c marxin at gcc dot gnu.org 2021-11-14 11:02 ` marxin at gcc dot gnu.org 2021-11-14 11:05 ` zhendong.su at inf dot ethz.ch 2021-11-14 11:08 ` aldyh at gcc dot gnu.org 2021-11-14 11:08 ` aldyh at gcc dot gnu.org 2021-11-14 15:37 ` zhendong.su at inf dot ethz.ch 2021-11-14 15:45 ` marxin at gcc dot gnu.org 2021-11-14 15:55 ` marxin at gcc dot gnu.org 2021-11-15 9:08 ` [Bug tree-optimization/103231] [12 Regression] ICE (nondeterministic/stack overflow) " rguenth at gcc dot gnu.org 2021-11-19 19:04 ` amacleod at redhat dot com 2021-11-24 14:06 ` cvs-commit at gcc dot gnu.org 2021-11-24 14:07 ` amacleod at redhat dot com 2021-11-29 14:31 ` law 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-103231-4-XloEp9pzPa@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).