public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112858] nvptx: 'unresolved symbol __cxa_thread_atexit_impl' Date: Tue, 05 Dec 2023 08:07:09 +0000 [thread overview] Message-ID: <bug-112858-4-5b8yo7rDK8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112858 --- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- Indeed in 'build-gcc/nvptx-none/libstdc++-v3/libsupc++/atexit_thread.o' I see: // BEGIN GLOBAL FUNCTION DECL: __cxa_thread_atexit_impl .extern .func (.param .u32 %value_out) __cxa_thread_atexit_impl (.param .u64 %in_ar0, .param .u64 %in_ar1, .param .u64 %in_ar2); That is, '.extern' instead of '.weak' linking directive, huh. ..., but still doing the NULL check: [...] .reg .u64 %r29; .reg .pred %r30; [...] mov.u64 %r29,__cxa_thread_atexit_impl; setp.eq.u64 %r30,%r29,0; @ %r30 bra $L9; .loc 2 156 37 { .param .u32 %value_in; .param .u64 %out_arg1; st.param.u64 [%out_arg1],%r26; .param .u64 %out_arg2; st.param.u64 [%out_arg2],%r27; .param .u64 %out_arg3; st.param.u64 [%out_arg3],%r28; call (%value_in),__cxa_thread_atexit_impl,(%out_arg1,%out_arg2,%out_arg3); ld.param.u32 %r34,[%value_in]; } mov.u32 %r25,%r34; .loc 2 156 59 bra $L8; $L9: [...]
next prev parent reply other threads:[~2023-12-05 8:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-05 7:49 [Bug target/112858] New: " tschwinge at gcc dot gnu.org 2023-12-05 8:07 ` tschwinge at gcc dot gnu.org [this message] 2023-12-05 8:18 ` [Bug target/112858] " tschwinge at gcc dot gnu.org 2023-12-05 19:09 ` [Bug libstdc++/112858] [14 Regression] " pinskia at gcc dot gnu.org 2023-12-05 23:23 ` dje at gcc dot gnu.org 2023-12-06 12:05 ` tschwinge at gcc dot gnu.org 2023-12-06 21:36 ` aoliva at gcc dot gnu.org 2023-12-07 3:56 ` cvs-commit at gcc dot gnu.org 2024-02-06 10:56 ` redi at gcc dot gnu.org 2024-03-27 13:48 ` [Bug libstdc++/112858] " rguenth 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-112858-4-5b8yo7rDK8@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).