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 d/99914] d: Template symbols not overridable by normal symbols Date: Wed, 14 Apr 2021 12:44:13 +0000 [thread overview] Message-ID: <bug-99914-4-5YgKOC2Os6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99914-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99914 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>: https://gcc.gnu.org/g:5b63eb17d863ac080cf3c7df08233054b09d3747 commit r11-8173-g5b63eb17d863ac080cf3c7df08233054b09d3747 Author: Iain Buclaw <ibuclaw@gdcproject.org> Date: Tue Apr 13 16:19:03 2021 +0200 d: Move call to set_linkage_for_decl to declare_extern_var. This both prevents against it being called twice for declarations that are defined, and fixes an issue where variables defined in the compilation get one kind of linkage (weak), and the same variables declared via declare_extern_var get another (extern). gcc/d/ChangeLog: PR d/99914 * decl.cc (DeclVisitor::visit (StructDeclaration *)): Don't set DECL_INSTANTIATED on static initializer declarations. (DeclVisitor::visit (ClassDeclaration *)): Likewise. (DeclVisitor::visit (EnumDeclaration *)): Likewise. (d_finish_decl): Move call to set_linkage_for_decl to... (declare_extern_var): ...here.
next prev parent reply other threads:[~2021-04-14 12:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-05 11:07 [Bug d/99914] New: " ibuclaw at gdcproject dot org 2021-04-05 11:41 ` [Bug d/99914] " cvs-commit at gcc dot gnu.org 2021-04-05 11:53 ` ibuclaw at gdcproject dot org 2021-04-14 12:44 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-14 13:02 ` ibuclaw at gdcproject dot org 2021-04-17 12:37 ` 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-99914-4-5YgKOC2Os6@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).