public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67453] vtable not emitted for class with no key method and defaulted destructor with attribute((used)) Date: Thu, 05 Nov 2020 16:02:31 +0000 [thread overview] Message-ID: <bug-67453-4-OsAKvKFsnJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67453-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67453 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |97729 Last reconfirmed|2015-09-04 00:00:00 |2020-11-5 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- We don't emit any constructors or destructors that are marked used. This is a problem for libstdc++ now. struct S { S(); ~S(); S(const S&); }; [[gnu::used]] inline S::S() { } [[gnu::used]] inline S::~S() { } [[gnu::used]] inline S::S(const S&) { } This generates no code with GCC. Clang emits all three functions. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97729 [Bug 97729] [11 Regression] Link failure due to basic_stringbuf and others when building DLL on MinGW
next prev parent reply other threads:[~2020-11-05 16:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-67453-4@http.gcc.gnu.org/bugzilla/> 2015-09-04 16:40 ` jason at gcc dot gnu.org 2020-11-05 16:02 ` redi at gcc dot gnu.org [this message] 2020-11-05 16:46 ` jakub at gcc dot gnu.org 2020-11-05 18:01 ` cvs-commit at gcc dot gnu.org 2020-11-06 19:35 ` cvs-commit at gcc dot gnu.org 2020-11-09 14:29 ` cvs-commit at gcc dot gnu.org 2020-11-12 10:05 ` cvs-commit 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-67453-4-OsAKvKFsnJ@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).