public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113987] [12/13/14 Regression] Binding a reference to an uninitialized data member should not cause -Wuninitialized
Date: Mon, 19 Feb 2024 05:32:01 +0000 [thread overview]
Message-ID: <bug-113987-4-Q8gsVAnU5F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113987-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Fangrui Song from comment #1)
> BTW,
> https://github.com/llvm/llvm-project/blob/main/clang/test/SemaCXX/
> uninitialized.cpp has many member initializer list examples
And r12-5391-g0790c8aacdfb4f added one testcase where clang produces a bogus
warning too so it goes both ways really :).
next prev parent reply other threads:[~2024-02-19 5:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 5:17 [Bug middle-end/113987] New: " i at maskray dot me
2024-02-19 5:18 ` [Bug middle-end/113987] " i at maskray dot me
2024-02-19 5:26 ` [Bug c++/113987] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-02-19 5:26 ` pinskia at gcc dot gnu.org
2024-02-19 5:32 ` pinskia at gcc dot gnu.org [this message]
2024-02-19 7:26 ` jakub at gcc dot gnu.org
2024-02-19 8:18 ` rguenth at gcc dot gnu.org
2024-02-20 15:41 ` mpolacek at gcc dot gnu.org
2024-02-20 20:54 ` mpolacek at gcc dot gnu.org
2024-02-21 13:53 ` mpolacek at gcc dot gnu.org
2024-02-29 17:41 ` cvs-commit at gcc dot gnu.org
2024-02-29 18:05 ` [Bug c++/113987] [12/13 " mpolacek at gcc dot gnu.org
2024-06-20 9:15 ` rguenth 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-113987-4-Q8gsVAnU5F@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).