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/103231] [12 Regression] ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault since r12-5014-g6b8b959675a3e14c Date: Sun, 14 Nov 2021 15:37:35 +0000 [thread overview] Message-ID: <bug-103231-4-skGGABi2mN@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 --- Comment #9 from Zhendong Su <zhendong.su at inf dot ethz.ch> --- A very simple repro (with ulimit -s 32): [530] % compile.sh small.c *** Compiling with: gcctk -O1 small.c gcctk: internal compiler error: Segmentation fault signal terminated program cc1 Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. *** Compiling with: gcc110 -O1 small.c [531] % [531] % cat small.c int a, b; int main() { int c, d; L1: if (a) { __builtin_printf("%d", d); L2: goto L1; } if (b) { d = c; goto L2; } return 0; } [532] % [532] % cat compile.sh #!/bin/bash ulimit -s 32 echo "*** Compiling with: gcctk -O1 $1" gcctk -O1 $1 echo echo "*** Compiling with: gcc110 -O1 $1" gcc110 -O1 $1 [533] %
next prev parent reply other threads:[~2021-11-14 15:37 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-14 10:31 [Bug tree-optimization/103231] New: ICE (nondeterministic) on valid code at -O1 on x86_64-linux-gnu: Segmentation fault 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 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 [this message] 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-skGGABi2mN@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).