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/114016] New: ICE: in AT_unsigned, at dwarf2out.cc:4592 with -march=armv9-a -gbtf or -gctf Date: Tue, 20 Feb 2024 19:15:37 +0000 [thread overview] Message-ID: <bug-114016-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114016 Bug ID: 114016 Summary: ICE: in AT_unsigned, at dwarf2out.cc:4592 with -march=armv9-a -gbtf or -gctf Product: gcc Version: 14.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: aarch64-unknown-linux-gnu Created attachment 57473 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57473&action=edit reduced testcase Compiler output: $ aarch64-unknown-linux-gnu-gcc -march=armv9-a -gbtf testcase.c testcase.c:2:1: internal compiler error: in AT_unsigned, at dwarf2out.cc:4592 2 | void fn_f64x4(svfloat64x4_t) {} | ^~~~ 0x7a2627 AT_unsigned(dw_attr_struct*) /repo/gcc-trunk/gcc/dwarf2out.cc:4592 0x7a433d AT_unsigned(dw_attr_struct*) /repo/gcc-trunk/gcc/dwarf2out.cc:4591 0xe43aee ctf_die_bitsize /repo/gcc-trunk/gcc/dwarf2ctf.cc:211 0xe4463e gen_ctf_sou_type /repo/gcc-trunk/gcc/dwarf2ctf.cc:526 0xe43f07 gen_ctf_type /repo/gcc-trunk/gcc/dwarf2ctf.cc:892 0xe43cc7 gen_ctf_function_type /repo/gcc-trunk/gcc/dwarf2ctf.cc:718 0xe44b53 gen_ctf_function /repo/gcc-trunk/gcc/dwarf2ctf.cc:853 0xe44b53 ctf_do_die(die_struct*) /repo/gcc-trunk/gcc/dwarf2ctf.cc:974 0xe99183 ctf_debug_do_cu /repo/gcc-trunk/gcc/dwarf2out.cc:33018 0xe99183 ctf_debug_do_cu /repo/gcc-trunk/gcc/dwarf2out.cc:33011 0xe99183 dwarf2out_early_finish /repo/gcc-trunk/gcc/dwarf2out.cc:33147 0xdf680f symbol_table::finalize_compilation_unit() /repo/gcc-trunk/gcc/cgraphunit.cc:2580 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. $ 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-r14-9077-20240220001758-g52490278466-checking-yes-rtl-df-extra-aarch64/bin/../libexec/gcc/aarch64-unknown-linux-gnu/14.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-r14-9077-20240220001758-g52490278466-checking-yes-rtl-df-extra-aarch64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.1 20240220 (experimental) (GCC)
reply other threads:[~2024-02-20 19:15 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-114016-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).