public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113331] AMDGCN: Compilation failure due to duplicate .LEHB<n>/.LEHE<n> symbols Date: Sat, 17 Feb 2024 02:17:39 +0000 [thread overview] Message-ID: <bug-113331-4-NkANXgcQlJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113331-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113331 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- All of the following is in except.cc. The problem is that the count in the label is relative to 'call_site_base'. In convert_to_eh_region_ranges, those get bumped - but the function reset it at the end. They do get accumulated via, e.g., dw2_output_call_site_table but, in GCN, the output_function_exception_table is exit early because of: 3229 if (!crtl->uses_eh_lsda 3230 || targetm_common.except_unwind_info (&global_options) == UI_NONE) 3231 return; Thus, the next time convert_to_eh_region_ranges is called, it starts with the very same numbers. The reason that this gets produced is because there is an ERT_MUST_NOT_THROW ("MUST_NOT_THROW regions prevent all exceptions from propagating. This region type is used in C++ to surround destructors being run inside a CLEANUP region.") As there are both "-1" (implies no action) and "-2" (MUST_NOT_THROW), GCN produces this output. For whatever reason, nvptx has no "-1" actions in the function, thus, after the change to "-2", there is no flip and - hence, no output is produced - avoiding the issue. → I bet that both gcn and nvptx are affected (unless luck or compiled with -fno-exceptions).
next prev parent reply other threads:[~2024-02-17 2:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-11 9:46 [Bug target/113331] New: " jules at gcc dot gnu.org 2024-01-11 10:42 ` [Bug target/113331] " rguenth at gcc dot gnu.org 2024-02-17 2:17 ` burnus at gcc dot gnu.org [this message] 2024-02-20 9:37 ` tschwinge at gcc dot gnu.org 2024-03-06 13:12 ` tschwinge 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-113331-4-NkANXgcQlJ@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).