public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/99830] New: [11 Regression] ICE: in lra_eliminate_regs_1, at lra-eliminations.c:659 with -O2 -fno-expensive-optimizations -fno-split-wide-types -g Date: Tue, 30 Mar 2021 14:11:18 +0000 [thread overview] Message-ID: <bug-99830-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99830 Bug ID: 99830 Summary: [11 Regression] ICE: in lra_eliminate_regs_1, at lra-eliminations.c:659 with -O2 -fno-expensive-optimizations -fno-split-wide-types -g Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: aarch64-unknown-linux-gnu Created attachment 50488 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50488&action=edit reduced testcase Compiler output: $ aarch64-unknown-linux-gnu-gcc -O2 -fno-expensive-optimizations -fno-split-wide-types -g testcase.c during RTL pass: reload testcase.c: In function 'foo': testcase.c:6:1: internal compiler error: in lra_eliminate_regs_1, at lra-eliminations.c:659 6 | } | ^ 0x73e41c lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:659 0xf16d42 lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:602 0xf16b3c lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:503 0xf16ba9 lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:507 0xf171ad lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:610 0xf16d42 lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:602 0xf16ba9 lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:507 0xf171ad lra_eliminate_regs_1(rtx_insn*, rtx_def*, machine_mode, bool, bool, poly_int<2u, long>, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:610 0xf183ff eliminate_regs_in_insn(rtx_insn*, bool, bool, poly_int<2u, long>) /repo/gcc-trunk/gcc/lra-eliminations.c:1023 0xf18f9d process_insn_for_elimination /repo/gcc-trunk/gcc/lra-eliminations.c:1333 0xf18f9d lra_eliminate(bool, bool) /repo/gcc-trunk/gcc/lra-eliminations.c:1401 0xefa038 lra(_IO_FILE*) /repo/gcc-trunk/gcc/lra.c:2470 0xeab919 do_reload /repo/gcc-trunk/gcc/ira.c:5835 0xeab919 execute /repo/gcc-trunk/gcc/ira.c:6021 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. $ aarch64-unknown-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-aarch64/bin/aarch64-unknown-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r11-7911-20210330134321-gf64b91568f3-checking-yes-rtl-df-extra-aarch64/bin/../libexec/gcc/aarch64-unknown-linux-gnu/11.0.1/lto-wrapper Target: aarch64-unknown-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --with-sysroot=/usr/aarch64-unknown-linux-gnu --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=aarch64-unknown-linux-gnu --with-ld=/usr/bin/aarch64-unknown-linux-gnu-ld --with-as=/usr/bin/aarch64-unknown-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r11-7911-20210330134321-gf64b91568f3-checking-yes-rtl-df-extra-aarch64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.0.1 20210330 (experimental) (GCC)
next reply other threads:[~2021-03-30 14:11 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-30 14:11 zsojka at seznam dot cz [this message] 2021-03-30 16:14 ` [Bug rtl-optimization/99830] " acoplan at gcc dot gnu.org 2021-03-31 7:53 ` rguenth at gcc dot gnu.org 2021-04-08 13:21 ` rguenth at gcc dot gnu.org 2021-04-08 13:27 ` jakub at gcc dot gnu.org 2021-04-08 14:45 ` [Bug debug/99830] " jakub at gcc dot gnu.org 2021-04-09 12:29 ` segher at gcc dot gnu.org 2021-04-09 12:36 ` jakub at gcc dot gnu.org 2021-04-09 12:38 ` segher at gcc dot gnu.org 2021-04-09 13:27 ` jakub at gcc dot gnu.org 2021-04-09 14:23 ` jakub at gcc dot gnu.org 2021-04-09 17:09 ` segher at gcc dot gnu.org 2021-04-09 17:31 ` jakub at gcc dot gnu.org 2021-04-09 18:01 ` segher at gcc dot gnu.org 2021-04-09 19:10 ` jakub at gcc dot gnu.org 2021-04-09 19:10 ` jakub at gcc dot gnu.org 2021-04-09 21:29 ` segher at gcc dot gnu.org 2021-04-12 16:20 ` jakub at gcc dot gnu.org 2021-04-12 23:01 ` cvs-commit at gcc dot gnu.org 2021-04-12 23:03 ` jakub at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:52 ` cvs-commit 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-99830-4@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).