public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot 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 13:02:59 +0000	[thread overview]
Message-ID: <bug-99914-4-GZ9i520Dsj@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 #4 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Weak declarations (both functions and variables) were found not to be working
at all on MinGW targets.  The only way that there desired behaviour can be
achieved there then is to mark *all* declarations with external linkage as
being DECL_ONE_ONLY, so they can override each other.

  parent reply	other threads:[~2021-04-14 13:02 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
2021-04-14 13:02 ` ibuclaw at gdcproject dot org [this message]
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-GZ9i520Dsj@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: link
Be 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).