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++/65816] Constructor delegation does not perform zero-initialization
Date: Tue, 01 Jun 2021 20:21:44 +0000	[thread overview]
Message-ID: <bug-65816-4-9z9sufmHyS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65816-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 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:ac0bc21bd634a334ba8f323c39a11f01dfdc2aae

commit r12-1153-gac0bc21bd634a334ba8f323c39a11f01dfdc2aae
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue Jun 1 12:23:49 2021 -0400

    c++: value-init vs zero-init in expand_aggr_init_1 [PR65816]

    In the case of value-initializing an object of class type T,
    [dcl.init.general]/8 says:

      - if T has either no default constructor ([class.default.ctor]) or
        a default constructor that is user-provided or deleted, then the
        object is default-initialized;
      - otherwise, the object is zero-initialized and ...  if T has a
        non-trivial default constructor, the object is default-initialized;

    But when determining whether to first zero-initialize the object,
    expand_aggr_init_1 incorrectly considers the user-providedness of _all_
    constructors rather than only that of the _default_ constructors.  This
    causes us to skip the zero-initialization step when the class type has a
    defaulted default constructor alongside a user-defined constructor.

    It seems the predicate type_has_non_user_provided_default_constructor
    accurately captures the above rule for when to first perform a
    zero-initialization during value-initialization, so this patch adjusts
    expand_aggr_init_1 to use this predicate instead.

            PR c++/65816

    gcc/cp/ChangeLog:

            * init.c (expand_aggr_init_1): Check
            type_has_non_user_provided_default_constructor instead of
            type_has_user_provided_constructor.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/constexpr-delegating3.C: New test.
            * g++.dg/cpp0x/dc10.C: New test.
            * g++.dg/cpp0x/initlist-base4.C: New test.
            * g++.dg/cpp2a/constexpr-init22.C: New test.

    libstdc++-v3/ChangeLog:

            * testsuite/23_containers/deque/allocator/default_init.cc,
            testsuite/23_containers/forward_list/allocator/default_init.cc,
            testsuite/23_containers/list/allocator/default_init.cc,
            testsuite/23_containers/map/allocator/default_init.cc,
            testsuite/23_containers/set/allocator/default_init.cc,
            testsuite/23_containers/vector/allocator/default_init.cc,
            testsuite/23_containers/vector/bool/allocator/default_init.cc:
            Remove xfail.

  parent reply	other threads:[~2021-06-01 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 16:22 [Bug c++/65816] New: " dyp-cpp at gmx dot net
2015-04-20 16:26 ` [Bug c++/65816] " redi at gcc dot gnu.org
2020-08-27 19:19 ` johelegp at gmail dot com
2021-05-31 13:53 ` zcsfjvvwjsgomjypri at twzhhq dot com
2021-06-01 17:37 ` ppalka at gcc dot gnu.org
2021-06-01 20:21 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-02 12:33 ` cvs-commit at gcc dot gnu.org
2021-09-01 14:24 ` ppalka at gcc dot gnu.org
2021-10-12 19:41 ` cvs-commit at gcc dot gnu.org
2021-11-26 16:34 ` cvs-commit 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-65816-4-9z9sufmHyS@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).