public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102036] -Wmismatched-tags doesn't warn for explicit instantations
Date: Tue, 14 Dec 2021 22:16:00 +0000	[thread overview]
Message-ID: <bug-102036-4-JTBK3emNeH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102036-4@http.gcc.gnu.org/bugzilla/>

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=103703

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
G++ also doesn't warn for more involved cases like the one in pr103703 (with
the ICE fixed):

template <typename T>
struct A
{
  struct B { };
};

template <typename T>
struct C
{
  friend class A<C>::B;       // { dg-warning "-Wmismatched-tags" "pr102036" {
xfail *-*-* } }
};

template struct C<int>;

Clang warns for the above but also suffers from a false positive below:

template <typename T>
struct D
{
  friend class A<D>::B;       // okay, specialized as class below
};

template <>
struct A<long>
{
  class B { };
};

template struct D<long>;

      parent reply	other threads:[~2021-12-14 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 11:30 [Bug c++/102036] New: " redi at gcc dot gnu.org
2021-08-24 13:43 ` [Bug c++/102036] " cvs-commit at gcc dot gnu.org
2021-08-24 14:40 ` msebor at gcc dot gnu.org
2021-12-14 22:16 ` msebor 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-102036-4-JTBK3emNeH@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).