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 libstdc++/109816] New: [14 Regression] r14-321 fix for PR108969 breaks NVPTX offloading due to __asm (".globl _ZSt21ios_base_library_initv") Date: Thu, 11 May 2023 17:55:05 +0000 [thread overview] Message-ID: <bug-109816-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109816 Bug ID: 109816 Summary: [14 Regression] r14-321 fix for PR108969 breaks NVPTX offloading due to __asm (".globl _ZSt21ios_base_library_initv") Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- Commit r14-321-g9a41d2cdbcd2af77a3a91a840a3a13f0eb39971b "libstdc++: Another attempt to ensure g++ 13+ compiled programs enforce gcc 13.2+ libstdc++.so.6 [PR108969]" breaks some offload compiling with nvptx. For instance, https://github.com/TApplencourt/OvO/blob/master/test_src/cpp/hierarchical_parallelism/reduction_add-complex_double/target__teams__parallel_for_simd.cpp fails to assemble with ptxas (either at compile time or at runtime) with: ptxas a.xnvptx-none.mkoffload.s, line 8; fatal : Parsing error near '.globl': syntax error The problem is the code: // #APP .globl _ZSt21ios_base_library_initv // #NO_APP Which the commit added to the header file as: #if !__has_attribute(__init_priority__) static ios_base::Init __ioinit; +#elif defined(_GLIBCXX_SYMVER_GNU) + __extension__ __asm (".globl _ZSt21ios_base_library_initv"); #endif * * * NOTE: With GCN offloading the program runs, presumably because the LLVM assembler (mc) does not choke on ".globl".
next reply other threads:[~2023-05-11 17:55 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 17:55 burnus at gcc dot gnu.org [this message] 2023-05-11 18:02 ` [Bug libstdc++/109816] [13/14 " pinskia at gcc dot gnu.org 2023-05-11 18:40 ` burnus at gcc dot gnu.org 2023-05-11 18:48 ` jakub at gcc dot gnu.org 2023-05-11 20:10 ` burnus at gcc dot gnu.org 2023-05-11 20:16 ` jakub at gcc dot gnu.org 2023-05-11 20:51 ` burnus at gcc dot gnu.org 2023-05-11 21:06 ` jakub at gcc dot gnu.org 2023-05-11 21:37 ` burnus at gcc dot gnu.org 2023-05-12 7:06 ` rguenth at gcc dot gnu.org 2023-05-12 14:30 ` cvs-commit at gcc dot gnu.org 2023-05-16 9:39 ` cvs-commit at gcc dot gnu.org 2023-05-16 13:24 ` burnus 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-109816-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).