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++/110031] [11/12/13/14 Regression] ICE with deprecated attribute and NTTP and diagnostic for deprecated printed out so much
Date: Thu, 07 Mar 2024 15:01:52 +0000	[thread overview]
Message-ID: <bug-110031-4-nptd3JbvWq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110031-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:9f915684624413f96e1a5ffada398ccd1c533e38

commit r14-9364-g9f915684624413f96e1a5ffada398ccd1c533e38
Author: Marek Polacek <polacek@redhat.com>
Date:   Mon Mar 4 12:35:18 2024 -0500

    c++: ICE with variable template and [[deprecated]] [PR110031]

    lookup_and_finish_template_variable already has and uses the complain
    parameter but it is not passing it down to mark_used so we got the
    default tf_warning_or_error, which causes various problems when
    lookup_and_finish_template_variable gets called with complain=tf_none.

            PR c++/110031

    gcc/cp/ChangeLog:

            * pt.cc (lookup_and_finish_template_variable): Pass complain to
            mark_used.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1z/inline-var11.C: New test.

  parent reply	other threads:[~2024-03-07 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 22:45 [Bug c++/110031] New: ICE: error reporting routines re-entered on non-type template argument stevenxia990430 at gmail dot com
2023-05-30  3:41 ` [Bug c++/110031] " pinskia at gcc dot gnu.org
2023-05-30  3:49 ` [Bug c++/110031] [10/11/12/13/14 Regression] ICE with deprecated attribute and NTTP and diagnostic for deprecated printed out so much pinskia at gcc dot gnu.org
2023-05-30  4:31 ` stevenxia990430 at gmail dot com
2023-07-07 10:45 ` [Bug c++/110031] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-01-12 13:57 ` rguenth at gcc dot gnu.org
2024-01-12 13:58 ` rguenth at gcc dot gnu.org
2024-03-04 17:10 ` mpolacek at gcc dot gnu.org
2024-03-04 17:15 ` mpolacek at gcc dot gnu.org
2024-03-07 15:01 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-07 15:02 ` [Bug c++/110031] [11/12/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-110031-4-nptd3JbvWq@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).