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++/86491] bogus and unsuppressible warning: 'YYY' has a base 'ZZZ' whose type uses the anonymous namespace
Date: Mon, 12 Sep 2022 16:09:57 +0000	[thread overview]
Message-ID: <bug-86491-4-CSt1NLYcsJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86491-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:8ef5fa4c56c82dfbd6e8fc5e4e08c4be843abc3e

commit r13-2627-g8ef5fa4c56c82dfbd6e8fc5e4e08c4be843abc3e
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jun 30 17:53:26 2022 +0100

    c++: Refer to internal linkage for -Wsubobject-linkage [PR86491]

    Since C++11 relaxed the requirement for template arguments to have
    external linkage, it's possible to get -Wsubobject-linkage warnings
    without using any anonymous namespaces. This confuses users when they
    get diagnostics that refer to an anonymous namespace that doesn't exist
    in their code.

    This changes the diagnostic to say "has internal linkage" for C++11 and
    later, if the type isn't actually a member of the anonymous namespace.
    Making that distinction involved renaming the current decl_anon_ns_mem_p to
    something that better expresses its semantics.

    For C++98 template arguments declared with 'static' are ill-formed
    anyway, so the only way this warning can arise is via anonymous
    namespaces. That means the existing wording is accurate for C++98 and so
    we can keep it.

            PR c++/86491

    gcc/cp/ChangeLog:

            * decl2.cc (constrain_class_visibility): Adjust wording of
            -Wsubobject-linkage for cases where anonymous
            namespaces aren't used.
            * tree.cc (decl_anon_ns_mem_p): Now only true for actual anonymous
            namespace members, rename old semantics to...
            (decl_internal_context_p): ...this.
            * cp-tree.h, name-lookup.cc, pt.cc: Adjust.

    gcc/testsuite/ChangeLog:

            * g++.dg/warn/anonymous-namespace-3.C: Use separate dg-warning
            directives for C++98 and everything else.
            * g++.dg/warn/Wsubobject-linkage-5.C: New test.

      parent reply	other threads:[~2022-09-12 16:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-86491-4@http.gcc.gnu.org/bugzilla/>
2021-11-10  4:57 ` pinskia at gcc dot gnu.org
2021-11-10  8:24 ` redi at gcc dot gnu.org
2021-11-10  9:01 ` redi at gcc dot gnu.org
2022-06-30  4:10 ` pinskia at gcc dot gnu.org
2022-06-30  4:13 ` pinskia at gcc dot gnu.org
2022-06-30  8:20 ` redi at gcc dot gnu.org
2022-07-04 12:15 ` redi at gcc dot gnu.org
2022-09-12 16:09 ` 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-86491-4-CSt1NLYcsJ@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).