public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gilles.gouaillardet at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100305] New: ICE in output_operand_lossage with -march=armv8.2-a -O3 Date: Wed, 28 Apr 2021 06:13:04 +0000 [thread overview] Message-ID: <bug-100305-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100305 Bug ID: 100305 Summary: ICE in output_operand_lossage with -march=armv8.2-a -O3 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gilles.gouaillardet at gmail dot com Target Milestone: --- Created attachment 50696 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50696&action=edit a (compressed) preprocessed reproducer This is a new bug with the g++ compiler I found when building GROMACS on aarch64 with -O3. -O2 works fine, and so does x86_64. I was only able to reproduce the issue on aarch64 (initially with SVE, but same outcome without it) The compiler crashed with the following stack trace: $ ~/local/gcc-latest/bin/g++ -c -O3 -march=armv8.2-a readpull.i during RTL pass: final readpull.cpp: In function 'std::vector<std::__cxx11::basic_string<char> > read_pullparams(std::vector<t_inpfile>*, pull_params_t*, warninp_t)': readpull.cpp:96:1: internal compiler error: output_operand: invalid expression as operand 96 | } | ^ 0xc66ab7 output_operand_lossage(char const*, ...) ../../../src/gcc-latest/gcc/final.c:3627 0xc67283 output_addr_const(_IO_FILE*, rtx_def*) ../../../src/gcc-latest/gcc/final.c:4184 0xc66d0f output_address(machine_mode, rtx_def*) ../../../src/gcc-latest/gcc/final.c:4085 0xc66c4b output_operand(rtx_def*, int) ../../../src/gcc-latest/gcc/final.c:4069 0xc6769f output_asm_insn(char const*, rtx_def**) ../../../src/gcc-latest/gcc/final.c:3981 0xc6b84f output_asm_insn(char const*, rtx_def**) ../../../src/gcc-latest/gcc/final.c:3858 0xc6b84f final_scan_insn_1 ../../../src/gcc-latest/gcc/final.c:3125 0xc6be43 final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*) ../../../src/gcc-latest/gcc/final.c:3171 0xc6bf63 final_1 ../../../src/gcc-latest/gcc/final.c:2022 0xc6cc0b rest_of_handle_final ../../../src/gcc-latest/gcc/final.c:4676 0xc6cc0b execute ../../../src/gcc-latest/gcc/final.c:4754 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.
next reply other threads:[~2021-04-28 6:13 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-28 6:13 gilles.gouaillardet at gmail dot com [this message] 2021-04-28 6:25 ` [Bug c++/100305] " acoplan at gcc dot gnu.org 2021-04-28 6:26 ` acoplan at gcc dot gnu.org 2021-04-28 6:27 ` acoplan at gcc dot gnu.org 2021-04-28 7:47 ` [Bug target/100305] [11/12 Regression] aarch64: ICE in output_operand_lossage with -O3 gilles.gouaillardet at gmail dot com 2021-04-28 7:50 ` pinskia at gcc dot gnu.org 2021-04-28 8:05 ` pinskia at gcc dot gnu.org 2021-04-28 9:50 ` rsandifo at gcc dot gnu.org 2021-04-28 16:55 ` cvs-commit at gcc dot gnu.org 2021-04-28 16:58 ` [Bug target/100305] [10/11/12 " rsandifo at gcc dot gnu.org 2021-04-29 8:28 ` cvs-commit at gcc dot gnu.org 2021-04-29 9:44 ` [Bug target/100305] [10 " cvs-commit at gcc dot gnu.org 2021-04-29 9:45 ` cvs-commit at gcc dot gnu.org 2021-04-30 1:40 ` gilles.gouaillardet at gmail dot com 2021-04-30 14:18 ` rsandifo at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-08-17 14:14 ` cvs-commit at gcc dot gnu.org 2021-08-17 14:16 ` rsandifo 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-100305-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).