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++/99213] Suboptimal pretty printing of local class type when type's context contains a class template specialization
Date: Thu, 25 Feb 2021 21:45:13 +0000	[thread overview]
Message-ID: <bug-99213-4-J2nkW2S2zl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99213-4@http.gcc.gnu.org/bugzilla/>

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

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

commit r11-7406-g7fb9a1e929db520fd741e60d84ec1a58581a8299
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Feb 25 16:44:34 2021 -0500

    c++: Fix pretty printing the context of local class [PR99213]

    My r10-7705 patch for PR94521 made us set TFF_NO_FUNCTION_ARGUMENTS when
    pretty printing the function scope of a local class type in order to
    eliminate infinite recursion with a function signature that contains
    decltype([]{}).  But due to the way dump_function_decl works, this
    change regressed our pretty printing of local class types whose context
    contains a class template specialization, as in the testcase below, in
    which we wrongly pretty print the two local types as 'A<T>::f<char>::S1'
    and 'B<T>::f<int>::S2'.

    This patch makes dump_scope pass TFF_NO_TEMPLATE_BINDINGS instead of
    TFF_NO_FUNCTION_ARGUMENTS when pretty printing a function scope.  It
    appears this is the strictly better flag to use: it avoids the infinite
    recursion issue, it restores pretty printing of the function parameter
    list, and it stops dump_function_decl from trying to print a function
    template specialization in its own weird way.

    Summary of pretty printing differences for the below testcase:

      r10-7704:   A<T>::f() [with U = char; T = int]::S1
                  B<T>::f() [with T = int]::S2

      r10-7705:   A<T>::f<char>::S1
                  B<T>::f<int>::S2

      this patch: A<int>::f<char>()::S1
                  B<int>::f()::S2

    gcc/cp/ChangeLog:

            PR c++/99213
            PR c++/94521
            * error.c (dump_scope): Pass TFF_NO_TEMPLATE_BINDINGS instead of
            TFF_NO_FUNCTION_ARGUMENTS when dumping a function scope.

    gcc/testsuite/ChangeLog:

            PR c++/99213
            PR c++/94521
            * g++.dg/diagnostic/local1.C: New test.

  parent reply	other threads:[~2021-02-25 21:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  3:39 [Bug c++/99213] New: Incorrect " ppalka at gcc dot gnu.org
2021-02-23  3:46 ` [Bug c++/99213] " ppalka at gcc dot gnu.org
2021-02-25 21:45 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-25 21:46 ` [Bug c++/99213] Suboptimal " ppalka 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-99213-4-J2nkW2S2zl@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).