public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dyp-cpp at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65816] New: Constructor delegation does not perform zero-initialization
Date: Mon, 20 Apr 2015 16:22:00 -0000 [thread overview]
Message-ID: <bug-65816-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65816
Bug ID: 65816
Summary: Constructor delegation does not perform
zero-initialization
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dyp-cpp at gmx dot net
In the following program, I expect the object `t` to be zero-initialized via
constructor delegation. Clang++ does this, but g++ 6.0 2015-04-20 does not.
-----------------------------
struct test
{
int m;
test() = default;
test(int) : test() {}
};
#include <iostream>
int main()
{
test t(0);
std::cout << t.m;
}
-----------------------------
While C++14 IS [class.base.init]p6 is unclear about this, as far as I can tell,
paragraph 7 implies (in the parenthesized clause) that the constructor
`test(int)` is required to value-initialize the object:
> The expression-list or braced-init-list in a mem-initializer is used to initialize the designated subobject (or, in the case of a delegating constructor, the complete class object) according to the initialization rules of 8.5 for direct-initialization.
The class `test` does not have a user-provided default constructor, hence
zero-initialization should be performed as per [dcl.init]p8.2
next reply other threads:[~2015-04-20 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 16:22 dyp-cpp at gmx dot net [this message]
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
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@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).