public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "m101010a at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106395] [12/13 regression] [mingw] "redeclared without dllimport attribute: previous dllimport ignored" on C++ friend
Date: Mon, 01 Aug 2022 16:10:57 +0000	[thread overview]
Message-ID: <bug-106395-4-Ie1OzEjjwG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106395-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106395

m101010a at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |m101010a at gmail dot com

--- Comment #1 from m101010a at gmail dot com ---
Git bisect indicates this was caused by commit
a0fdff3cf33f72848d3f894272431a5d49fe6a16 "c++: Fix friend attributes
[PR51344]".
Also, you don't need a member variable to trigger this; I was able to reproduce
it with just

__attribute__((dllimport)) void f();
struct s
{
        friend __attribute__((dllimport)) void f();
};

  parent reply	other threads:[~2022-08-01 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 21:17 [Bug c++/106395] New: [10/11 " thiago at kde dot org
2022-07-22  7:12 ` [Bug c++/106395] [12/13 " rguenth at gcc dot gnu.org
2022-08-01 16:10 ` m101010a at gmail dot com [this message]
2022-08-10 13:15 ` [Bug c++/106395] [12/13 regression] [mingw] "redeclared without dllimport attribute: previous dllimport ignored" on C++ friend since r12-299-ga0fdff3cf33f72 rguenth at gcc dot gnu.org
2022-12-26 15:15 ` nightstrike at gmail dot com
2023-01-17 18:51 ` i.nixman at autistici dot org
2023-05-08 12:25 ` [Bug c++/106395] [12 " rguenth 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-106395-4-Ie1OzEjjwG@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).