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++/100596] [12 Regression] error: attribute appertains to a friend declaration that is not a definition since r12-786-g149061188c7c6ddf
Date: Wed, 19 May 2021 17:10:44 +0000	[thread overview]
Message-ID: <bug-100596-4-Kx0VztLDHM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100596-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:adcb497bdba499d161d2e5e8de782bdd6f75d62c

commit r12-925-gadcb497bdba499d161d2e5e8de782bdd6f75d62c
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue May 18 16:11:16 2021 -0400

    c++: Relax attribute on friend declaration checking [PR100596]

    It turned out that there are codebases that profusely use GNU attributes
    on friend declarations, so we have to dial back our checking and allow
    them.  And for C++11 attributes let's just warn instead of giving
    errors.

            PR c++/100596

    gcc/cp/ChangeLog:

            * cp-tree.h (any_non_type_attribute_p): Remove.
            * decl.c (grokdeclarator): Turn an error into a warning and only
            warn for standard attributes.
            * decl2.c (any_non_type_attribute_p): Remove.
            * parser.c (cp_parser_elaborated_type_specifier): Turn an error
            into a warning and only warn for standard attributes.
            (cp_parser_member_declaration): Likewise.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/friend7.C: Turn a few dg-warnings into dg-errors.
            Remove dg-errors for GNU attributes.
            * g++.dg/ext/attrib63.C: Remove dg-error.
            * g++.dg/cpp0x/friend8.C: New test.

  parent reply	other threads:[~2021-05-19 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  7:47 [Bug c++/100596] New: " marxin at gcc dot gnu.org
2021-05-14  7:48 ` [Bug c++/100596] " marxin at gcc dot gnu.org
2021-05-14 12:45 ` mpolacek at gcc dot gnu.org
2021-05-14 14:13 ` marxin at gcc dot gnu.org
2021-05-14 14:33 ` jason at gcc dot gnu.org
2021-05-14 17:04 ` mpolacek at gcc dot gnu.org
2021-05-19 17:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-19 17:13 ` mpolacek 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-100596-4-Kx0VztLDHM@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).