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++/99536] unexplained warning on "uninitialized value" in std::normal_distribution Date: Thu, 11 Mar 2021 17:53:44 +0000 [thread overview] Message-ID: <bug-99536-4-9z9G0b4yrv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99536-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99536 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:67e397660611990efd98f9e4106c1ee81f6803a4 commit r11-7627-g67e397660611990efd98f9e4106c1ee81f6803a4 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.
next prev parent reply other threads:[~2021-03-11 17:53 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-11 1:36 [Bug c++/99536] New: unexplained warning on "uninitialized value" wuz73 at hotmail dot com 2021-03-11 13:30 ` [Bug c++/99536] unexplained warning on "uninitialized value" in std::normal_distribution redi at gcc dot gnu.org 2021-03-11 15:09 ` redi at gcc dot gnu.org 2021-03-11 17:53 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-11 18:18 ` redi at gcc dot gnu.org 2021-03-29 20:03 ` cvs-commit at gcc dot gnu.org 2021-03-29 21:37 ` redi at gcc dot gnu.org 2021-04-07 21:16 ` [Bug tree-optimization/99536] " msebor at gcc dot gnu.org 2021-04-07 21:18 ` msebor at gcc dot gnu.org 2021-04-20 18:52 ` cvs-commit at gcc dot gnu.org 2022-08-06 2:57 ` wuz73 at hotmail dot com
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-99536-4-9z9G0b4yrv@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: 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).