public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109809] New: ICE in dwarf2out_frame_debug_cfa_offset, at dwarf2cfi.cc:1376 Date: Thu, 11 May 2023 09:36:22 +0000 [thread overview] Message-ID: <bug-109809-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109809 Bug ID: 109809 Summary: ICE in dwarf2out_frame_debug_cfa_offset, at dwarf2cfi.cc:1376 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jamborm at gcc dot gnu.org Target Milestone: --- Host: x86_64-linux Target: s390x-linux-gnu-gcc With cross compiler configured as /home/worker/buildworker/tiber-gcc-trunk-s390x/build/configure --enable-languages=c,c++,fortran,rust,m2 --disable-bootstrap --disable-libsanitizer --disable-multilib --enable-checking=release --prefix=/home/worker/cross --target=s390x-linux-gnu --with-as=/usr/bin/s390x-suse-linux-as running: ~/cross/bin/s390x-linux-gnu-gcc /home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.dg/tree-ssa/ldist-9.c -fstack-clash-protection -mpreserve-args -Ofast --param=stack-clash-protection-probe-interval=10 Results in: during RTL pass: dwarf2 /home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.dg/tree-ssa/ldist-9.c: In function ‘loop1’: /home/worker/buildworker/tiber-option-juggler/build/gcc/testsuite/gcc.dg/tree-ssa/ldist-9.c:23:1: internal compiler error: in dwarf2out_frame_debug_cfa_offset, at dwarf2cfi.cc:1376 23 | } | ^ 0x606f65 dwarf2out_frame_debug_cfa_offset /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:1376 0x606f65 dwarf2out_frame_debug /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:2285 0x606f65 scan_insn_after /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:2726 0x7efb77 scan_trace /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:2893 0x7efed5 create_cfi_notes /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:2938 0x7efed5 execute_dwarf2_frame /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:3309 0x7efed5 execute /home/worker/buildworker/tiber-gcc-trunk-s390x/build/gcc/dwarf2cfi.cc:3799
next reply other threads:[~2023-05-11 9:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 9:36 jamborm at gcc dot gnu.org [this message] 2024-02-05 17:05 ` [Bug target/109809] " giulio.benetti at benettiengineering dot com 2024-02-05 17:07 ` giulio.benetti at benettiengineering dot com 2024-02-05 17:14 ` pinskia at gcc dot gnu.org 2024-02-05 17:31 ` giulio.benetti at benettiengineering 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-109809-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).