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 libstdc++/103549] [12 regression] Uninitialized member warning from regex header Date: Sat, 04 Dec 2021 15:55:12 +0000 [thread overview] Message-ID: <bug-103549-4-YG7JYD00dG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103549 --- 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:87710ec7b213245ecb194b778e97ae3a6790394f commit r12-5792-g87710ec7b213245ecb194b778e97ae3a6790394f Author: Jonathan Wakely <jwakely@redhat.com> Date: Sat Dec 4 11:38:25 2021 +0000 libstdc++: Initialize member in std::match_results [PR103549] This fixes a -Wuninitialized warning for std::cmatch m1, m2; m1=m2; Also name the template parameters in the forward declaration, to get rid of the <template-parameter-1-1> noise in diagnostics. libstdc++-v3/ChangeLog: PR libstdc++/103549 * include/bits/regex.h (match_results): Give names to template parameters in first declaration. (match_results::_M_begin): Add default member-initializer.
next prev parent reply other threads:[~2021-12-04 15:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-03 23:46 [Bug libstdc++/103549] New: " sss@li-snyder.org 2021-12-04 1:00 ` [Bug libstdc++/103549] " redi at gcc dot gnu.org 2021-12-04 15:55 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-06 8:21 ` rguenth at gcc dot gnu.org 2021-12-06 10:39 ` [Bug libstdc++/103549] " redi at gcc dot gnu.org 2022-01-05 22:06 ` cvs-commit at gcc dot gnu.org 2022-01-05 22:06 ` cvs-commit at gcc dot gnu.org 2022-01-05 22:08 ` redi at gcc dot gnu.org 2022-05-09 16:39 ` cvs-commit at gcc dot gnu.org 2022-05-09 19:44 ` redi 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-103549-4-YG7JYD00dG@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).