public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109816] [13/14 Regression] r14-321 fix for PR108969 breaks NVPTX offloading due to __asm (".globl _ZSt21ios_base_library_initv") Date: Tue, 16 May 2023 09:39:43 +0000 [thread overview] Message-ID: <bug-109816-4-5E76hReD9c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109816-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109816 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:7fb7d49b3c7129fa8a6b500f260abc642929361b commit r13-7335-g7fb7d49b3c7129fa8a6b500f260abc642929361b Author: Tobias Burnus <tobias@codesourcery.com> Date: Fri May 12 16:27:40 2023 +0200 LTO: Fix writing of toplevel asm with offloading [PR109816] When offloading was enabled, top-level 'asm' were added to the offloading section, confusing assemblers which did not support the syntax. Additionally, with offloading and -flto, the top-level assembler code did not end up in the host files. As r14-321-g9a41d2cdbcd added top-level 'asm' to one libstdc++ header file, the issue became more apparent, causing fails with nvptx for some C++ testcases. PR libstdc++/109816 gcc/ChangeLog: * lto-cgraph.cc (output_symtab): Guard lto_output_toplevel_asms by '!lto_stream_offload_p'. libgomp/ChangeLog: * testsuite/libgomp.c++/target-map-class-1.C: New test. * testsuite/libgomp.c++/target-map-class-2.C: New test. (cherry picked from commit a835f046cdf017b9e8ad5576df4f10daaf8420d0)
next prev parent reply other threads:[~2023-05-16 9:39 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 17:55 [Bug libstdc++/109816] New: [14 " burnus at gcc dot gnu.org 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 [this message] 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-5E76hReD9c@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).