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++/111471] Incorrect NTTP printing in the error messages
Date: Wed, 20 Sep 2023 16:11:49 +0000	[thread overview]
Message-ID: <bug-111471-4-7qs5GkKyQH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111471-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:75c4b0cde4835b45350da0a5cd82f1d1a0a7a2f1

commit r14-4178-g75c4b0cde4835b45350da0a5cd82f1d1a0a7a2f1
Author: Patrick Palka <ppalka@redhat.com>
Date:   Wed Sep 20 12:09:36 2023 -0400

    c++: improve class NTTP object pretty printing [PR111471]

    1. Move class NTTP object pretty printing to a more general spot in
       the pretty printer, so that we always print its value instead of
       its (mangled) name even when it appears outside of a template
       argument list.
    2. Print the type of an class NTTP object alongside its CONSTRUCTOR
       value, like dump_expr would have done.
    3. Don't print const VIEW_CONVERT_EXPR wrappers for class NTTPs.

            PR c++/111471

    gcc/cp/ChangeLog:

            * cxx-pretty-print.cc (cxx_pretty_printer::expression)
            <case VAR_DECL>: Handle class NTTP objects by printing
            their type and value.
            <case VIEW_CONVERT_EXPR>: Strip const VIEW_CONVERT_EXPR
            wrappers for class NTTPs.
            (pp_cxx_template_argument_list): Don't handle class NTTP
            objects here.

    gcc/testsuite/ChangeLog:

            * g++.dg/concepts/diagnostic19.C: New test.

  parent reply	other threads:[~2023-09-20 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  7:33 [Bug c++/111471] New: " mateusz.pusz at gmail dot com
2023-09-19 16:17 ` [Bug c++/111471] " ppalka at gcc dot gnu.org
2023-09-20 16:11 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-22 10:32 ` cvs-commit at gcc dot gnu.org
2024-05-21  9:17 ` jakub 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-111471-4-7qs5GkKyQH@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).