public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r10-9592] libstdc++: Initialize std::normal_distribution::_M_saved [PR 99536] Date: Mon, 29 Mar 2021 20:03:16 +0000 (GMT) [thread overview] Message-ID: <20210329200316.24D3E3850423@sourceware.org> (raw) https://gcc.gnu.org/g:039fc1ff2b018aaba5203c89de64ddc02c7a5c17 commit r10-9592-g039fc1ff2b018aaba5203c89de64ddc02c7a5c17 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Mar 11 16:43:51 2021 +0000 libstdc++: Initialize std::normal_distribution::_M_saved [PR 99536] This avoids a false positive -Wmaybe-uninitialized warning, by initializing _M_saved on construction. libstdc++-v3/ChangeLog: PR libstdc++/99536 * include/bits/random.h (normal_distribution): Use default-initializer for _M_saved and _M_saved_available. (cherry picked from commit 67e397660611990efd98f9e4106c1ee81f6803a4) Diff: --- libstdc++-v3/include/bits/random.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/include/bits/random.h b/libstdc++-v3/include/bits/random.h index 0be1191e07d..cba11299360 100644 --- a/libstdc++-v3/include/bits/random.h +++ b/libstdc++-v3/include/bits/random.h @@ -2022,12 +2022,12 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION explicit normal_distribution(result_type __mean, result_type __stddev = result_type(1)) - : _M_param(__mean, __stddev), _M_saved_available(false) + : _M_param(__mean, __stddev) { } explicit normal_distribution(const param_type& __p) - : _M_param(__p), _M_saved_available(false) + : _M_param(__p) { } /** @@ -2164,8 +2164,8 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION const param_type& __p); param_type _M_param; - result_type _M_saved; - bool _M_saved_available; + result_type _M_saved = 0; + bool _M_saved_available = false; }; /**
reply other threads:[~2021-03-29 20:03 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210329200316.24D3E3850423@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).