public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giulio.benetti at benettiengineering dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109809] ICE in dwarf2out_frame_debug_cfa_offset, at dwarf2cfi.cc:1376 Date: Mon, 05 Feb 2024 17:31:19 +0000 [thread overview] Message-ID: <bug-109809-4-1CTpMJTySX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109809-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109809 --- Comment #4 from Giulio Benetti <giulio.benetti at benettiengineering dot com> --- It's not a problem, but it looks very similar to me: CommandScreen.c:54:1: internal compiler error: in dwarf2out_frame_debug_cfa_offset, at dwarf2cfi.cc:1376 54 | } | ^ 0x16c6616 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char const*, __va_list_tag (*) [1], diagnostic_t) ???:0 0x16c72c7 internal_error(char const*, ...) ???:0 0x6a2d91 fancy_abort(char const*, int, char const*) ???:0 0x671146 dwarf2out_frame_debug(rtx_insn*) [clone .cold] ???:0 0x8645ef scan_trace(dw_trace_info*, bool) [clone .constprop.0] ???:0 0x864bf9 (anonymous namespace)::pass_dwarf2_frame::execute(function*) ???:0 Let me know if you still want me to open new bug. Thank you!
prev parent reply other threads:[~2024-02-05 17:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 9:36 [Bug target/109809] New: " jamborm at gcc dot gnu.org 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 [this message]
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-1CTpMJTySX@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).