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++/74762] [9/10/11 Regression] missing uninitialized warning (C++, parenthesized expr, TREE_NO_WARNING) Date: Mon, 28 Jun 2021 21:20:37 +0000 [thread overview] Message-ID: <bug-74762-4-vwan0091FT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-74762-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74762 --- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>: https://gcc.gnu.org/g:40c64c9ea565230817f08b5e66a30a1c94ec880c commit r12-1861-g40c64c9ea565230817f08b5e66a30a1c94ec880c Author: Martin Sebor <msebor@redhat.com> Date: Mon Jun 28 15:14:50 2021 -0600 Regression tests for TREE_NO_WARNING enhancement to warning groups [PR74765, PR74762]. PR middle-end/74765 - missing uninitialized warning (parenthesis, TREE_NO_WARNING abuse) PR middle-end/74762 - [9/10/11/12 Regression] missing uninitialized warning (C++, parenthesized expr, TREE_NO_WARNING) gcc/testsuite/ChangeLog: * g++.dg/uninit-pr74762.C: New test. * g++.dg/warn/uninit-pr74765.C: Same.
prev parent reply other threads:[~2021-06-28 21:20 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-74762-4@http.gcc.gnu.org/bugzilla/> 2021-04-16 19:44 ` [Bug c++/74762] [8/9/10/11 " msebor at gcc dot gnu.org 2021-05-14 9:48 ` [Bug c++/74762] [9/10/11/12 " jakub at gcc dot gnu.org 2021-05-24 22:18 ` msebor at gcc dot gnu.org 2021-06-01 8:08 ` rguenth at gcc dot gnu.org 2021-06-26 15:15 ` egallager at gcc dot gnu.org 2021-06-28 20:13 ` [Bug c++/74762] [9/10/11 " msebor at gcc dot gnu.org 2021-06-28 21:20 ` cvs-commit at gcc dot gnu.org [this message]
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-74762-4-vwan0091FT@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).