public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113541] Rejects __attribute__((section)) on explicit instantiation declaration of ctor/dtor Date: Tue, 23 Jan 2024 07:46:00 +0000 [thread overview] Message-ID: <bug-113541-4-wgY8TWIuHU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113541-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113541 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rejects-valid Version|unknown |14.0 Known to work| |4.9.4 Known to fail| |5.1.0 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- It sounds like an issue with the C++ mandated aliases. But I'll note that the template instantiations have to adhere to certain linkage so I wonder if simply putting them into a different section isn't going to break the ABI.
prev parent reply other threads:[~2024-01-23 7:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-22 15:21 [Bug c++/113541] New: " arthur.j.odwyer at gmail dot com 2024-01-22 20:16 ` [Bug c++/113541] " mpolacek at gcc dot gnu.org 2024-01-23 7:46 ` rguenth at gcc dot gnu.org [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-113541-4-wgY8TWIuHU@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).