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++/90451] [9/10/11/12 Regression] "static" function which added "deprecated" print deprecated warning >1 times (twice or even 3 times)
Date: Mon, 12 Sep 2022 20:30:00 +0000	[thread overview]
Message-ID: <bug-90451-4-SRIU0sfkpd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90451-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:999638cb7b126d33d1ea6548c69ba387b7d7a270

commit r12-8758-g999638cb7b126d33d1ea6548c69ba387b7d7a270
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Sep 12 13:47:34 2022 -0400

    c++: auto member function and auto variable [PR106893]

    As with PR105623, we need to call mark_single_function sooner to
    resolve the type of a BASELINK.

            PR c++/106893
            PR c++/90451

    gcc/cp/ChangeLog:

            * decl.cc (cp_finish_decl): Call mark_single_function.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1y/auto-fn65.C: New test.

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90451-4@http.gcc.gnu.org/bugzilla/>
2021-04-08 18:02 ` [Bug c++/90451] [8/9/10/11 " jason at gcc dot gnu.org
2021-04-09 13:53 ` jason at gcc dot gnu.org
2021-05-14  9:51 ` [Bug c++/90451] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:14 ` rguenth at gcc dot gnu.org
2022-02-17 21:22 ` cvs-commit at gcc dot gnu.org
2022-02-17 22:55 ` jason at gcc dot gnu.org
2022-09-12 19:47 ` cvs-commit at gcc dot gnu.org
2022-09-12 20:30 ` 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-90451-4-SRIU0sfkpd@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).