public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100626] [11/12 Regression] ICE Segmentation fault (during RTL pass: split1) since r11-165-geb72dc663e9070b2 Date: Mon, 17 May 2021 18:09:15 +0000 [thread overview] Message-ID: <bug-100626-4-qx7gNLwOFa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100626-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100626 --- Comment #4 from Haoxin Tu <haoxintu at gmail dot com> --- I found that it also crashes (under -O1 and -Os) on today's trunk version of GCC. $cat small.c #include <stdint.h> int a; void b() { int c; uint64_t *d = &c; uint8_t *e; if (a) *d &= *e; if (*d) for (;;) ; } $gcc -w -O1 -m32 small.c (or -Os) during RTL pass: split1 small.c: In function ‘b’: small.c:12:1: internal compiler error: Segmentation fault 12 | } | ^ 0xba0cef crash_signal ../../gcc/toplev.c:327 0xefc40a ix86_fixup_binary_operands(rtx_code, machine_mode, rtx_def**) ../../gcc/config/i386/i386-expand.c:900 0xefc5bb ix86_expand_binary_operator(rtx_code, machine_mode, rtx_def**) ../../gcc/config/i386/i386-expand.c:943 0x1214538 gen_andsi3(rtx_def*, rtx_def*, rtx_def*) ../../gcc/config/i386/i386.md:9091 0x12147b4 gen_split_191(rtx_insn*, rtx_def**) ../../gcc/config/i386/i386.md:9123 0x13f8f22 split_insns(rtx_def*, rtx_insn*) ../../gcc/config/i386/i386.md:14140 0x87e61e try_split(rtx_def*, rtx_insn*, int) ../../gcc/emit-rtl.c:3786 0xb15ad1 split_insn ../../gcc/recog.c:3363 0xb1af47 split_all_insns() ../../gcc/recog.c:3467 0xb1afd8 execute ../../gcc/recog.c:4385 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/gcc/build/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --prefix=/home/haoxin/haoxin-data/dut-research/compilers/gcc/build/ --enable-bootstrap --enable-checking=release --enable-languages=c,c++ --enable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 12.0.0 20210517 (experimental) (GCC)
next prev parent reply other threads:[~2021-05-17 18:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-16 18:05 [Bug tree-optimization/100626] New: ICE Segmentation fault (during RTL pass: split1) haoxintu at gmail dot com 2021-05-17 1:54 ` [Bug target/100626] " haoxintu at gmail dot com 2021-05-17 8:08 ` [Bug target/100626] [11/12 Regression] ICE Segmentation fault (during RTL pass: split1) since r11-165-geb72dc663e9070b2 marxin at gcc dot gnu.org 2021-05-17 8:53 ` jakub at gcc dot gnu.org 2021-05-17 11:26 ` ubizjak at gmail dot com 2021-05-17 12:49 ` rguenth at gcc dot gnu.org 2021-05-17 18:09 ` haoxintu at gmail dot com [this message] 2021-05-17 18:37 ` ubizjak at gmail dot com 2021-05-18 13:46 ` cvs-commit at gcc dot gnu.org 2021-05-25 17:22 ` cvs-commit at gcc dot gnu.org 2021-05-25 17:23 ` ubizjak at gmail dot com
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-100626-4-qx7gNLwOFa@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).