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++/115114] aggregate initialization with parens fails when there is a base class
Date: Fri, 17 May 2024 13:03:13 +0000	[thread overview]
Message-ID: <bug-115114-4-keT1KEHmA9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115114-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from GCC 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:5aaf47cb1987bbc5508c4b9b7dad5ea7d69af2c2

commit r15-630-g5aaf47cb1987bbc5508c4b9b7dad5ea7d69af2c2
Author: Patrick Palka <ppalka@redhat.com>
Date:   Fri May 17 09:02:52 2024 -0400

    c++: aggregate CTAD w/ paren init and bases [PR115114]

    During aggregate CTAD with paren init, we're accidentally overlooking
    base classes since TYPE_FIELDS of a template type doesn't contain
    corresponding base fields.  So we need to consider them separately.

            PR c++/115114

    gcc/cp/ChangeLog:

            * pt.cc (maybe_aggr_guide): Consider bases in the paren init case.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/class-deduction-aggr15.C: New test.

    Reviewed-by: Jason Merrill <jason@redhat.com>

  parent reply	other threads:[~2024-05-17 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 20:52 [Bug c++/115114] New: " eric.niebler at gmail dot com
2024-05-17  4:47 ` [Bug c++/115114] " pinskia at gcc dot gnu.org
2024-05-17 13:03 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-20 13:51 ` cvs-commit at gcc dot gnu.org
2024-05-20 13:53 ` 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-115114-4-keT1KEHmA9@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).