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++/100752] [11/12 Regression] error: cannot call member function ‘void S::f()’ without object
Date: Sat, 26 Jun 2021 00:12:20 +0000	[thread overview]
Message-ID: <bug-100752-4-KWG81GPjzQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100752-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:f9c80eb12c58126a94ad869380af5b88b752c06f

commit r12-1822-gf9c80eb12c58126a94ad869380af5b88b752c06f
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Jun 8 17:44:13 2021 -0400

    c++: Failure to delay noexcept parsing with ptr-operator [PR100752]

    We weren't passing 'flags' to the recursive call to cp_parser_declarator
    in the ptr-operator case and as an effect, delayed parsing of noexcept
    didn't work as advertised.  The following change passes more than just
    CP_PARSER_FLAGS_DELAY_NOEXCEPT but that doesn't seem to break anything.

    I'm now also passing member_p and static_p, as a consequence, two tests
    needed small tweaks.

            PR c++/100752

    gcc/cp/ChangeLog:

            * parser.c (cp_parser_declarator): Pass flags down to
            cp_parser_declarator.  Also pass static_p/member_p.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/noexcept69.C: New test.
            * g++.dg/parse/saved1.C: Adjust dg-error.
            * g++.dg/template/crash50.C: Likewise.

  parent reply	other threads:[~2021-06-26  0:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  9:01 [Bug c++/100752] New: [11/12 Regression] redi at gcc dot gnu.org
2021-05-25  9:03 ` [Bug c++/100752] [11/12 Regression] error: cannot call member function ‘void S::f()’ without object redi at gcc dot gnu.org
2021-05-25  9:14 ` rguenth at gcc dot gnu.org
2021-05-26 19:24 ` jason at gcc dot gnu.org
2021-05-26 19:35 ` jason at gcc dot gnu.org
2021-05-26 19:35 ` jason at gcc dot gnu.org
2021-05-26 19:40 ` mpolacek at gcc dot gnu.org
2021-06-08 21:10 ` mpolacek at gcc dot gnu.org
2021-06-08 21:12 ` jason at gcc dot gnu.org
2021-06-26  0:12 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-26  0:12 ` [Bug c++/100752] [11 " mpolacek at gcc dot gnu.org
2021-06-29 13:18 ` cvs-commit at gcc dot gnu.org
2021-06-29 13:19 ` 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-100752-4-KWG81GPjzQ@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).