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 target/104540] New: ICE: SIGSEGV in cfi_oprnd_equal_p with -O2 -fharden-conditional-branches -mforce-drap -mstackrealign --param=max-grow-copy-bb-insns=125 Date: Tue, 15 Feb 2022 05:16:51 +0000 [thread overview] Message-ID: <bug-104540-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104540 Bug ID: 104540 Summary: ICE: SIGSEGV in cfi_oprnd_equal_p with -O2 -fharden-conditional-branches -mforce-drap -mstackrealign --param=max-grow-copy-bb-insns=125 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 52442 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52442&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -O2 -fharden-conditional-branches -mforce-drap -mstackrealign --param=max-grow-copy-bb-insns=125 testcase.C during RTL pass: dwarf2 testcase.C: In function 'void foo()': testcase.C:19:1: internal compiler error: Segmentation fault 19 | } | ^ 0x166367f crash_signal /repo/gcc-trunk/gcc/toplev.cc:322 0x11e1770 cfa_reg::operator==(cfa_reg const&) const /repo/gcc-trunk/gcc/dwarf2out.h:144 0x11e1770 cfa_equal_p(dw_cfa_location const*, dw_cfa_location const*) /repo/gcc-trunk/gcc/dwarf2cfi.cc:765 0x11e1a99 cfi_row_equal_p /repo/gcc-trunk/gcc/dwarf2cfi.cc:831 0x11e534a maybe_record_trace_start /repo/gcc-trunk/gcc/dwarf2cfi.cc:2565 0x11e590b create_trace_edges /repo/gcc-trunk/gcc/dwarf2cfi.cc:2679 0x11e5f16 scan_trace /repo/gcc-trunk/gcc/dwarf2cfi.cc:2903 0x11e7303 create_cfi_notes /repo/gcc-trunk/gcc/dwarf2cfi.cc:2930 0x11e7303 execute_dwarf2_frame /repo/gcc-trunk/gcc/dwarf2cfi.cc:3301 0x11e7303 execute /repo/gcc-trunk/gcc/dwarf2cfi.cc:3789 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r12-7228-20220214143106-g0a1a3afb5fb-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/12.0.1/lto-wrapper Target: x86_64-pc-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 --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r12-7228-20220214143106-g0a1a3afb5fb-checking-yes-rtl-df-extra-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.0.1 20220214 (experimental) (GCC)
next reply other threads:[~2022-02-15 5:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 5:16 zsojka at seznam dot cz [this message] 2022-02-17 13:01 ` [Bug middle-end/104540] " aoliva at gcc dot gnu.org 2022-02-17 13:41 ` aoliva at gcc dot gnu.org 2022-02-25 1:19 ` cvs-commit at gcc dot gnu.org 2022-02-25 1:43 ` aoliva 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-104540-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).