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 c++/67453] vtable not emitted for class with no key method and defaulted destructor with attribute((used)) Date: Thu, 12 Nov 2020 10:05:55 +0000 [thread overview] Message-ID: <bug-67453-4-GxExYDsIHj@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 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:921661beb90edd14a6102e87f0ff71b5a21a70ee commit r10-9010-g921661beb90edd14a6102e87f0ff71b5a21a70ee Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Nov 6 20:33:39 2020 +0100 c++: Propagate attributes to clones in duplicate_decls [PR67453] On the following testcase where the cdtor attributes aren't on the in-class declaration but on an out-of-class definition, the cdtors have their clones created from the in-class declaration, and later on duplicate_decls updates attributes on the abstract cdtors, but nothing propagates them to the clones. 2020-11-06 Jakub Jelinek <jakub@redhat.com> PR c++/67453 * decl.c (duplicate_decls): Propagate DECL_ATTRIBUTES and DECL_PRESERVE_P from olddecl to its clones if any. * g++.dg/ext/attr-used-2.C: New test. (cherry picked from commit 6c282c14d1be0bba2bf5d49acd074b349f28ad17)
prev parent reply other threads:[~2020-11-12 10:05 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 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 [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-67453-4-GxExYDsIHj@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).