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:26:02 +0000 [thread overview] Message-ID: <bug-113987-4-R54Ybnc5Yv@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 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.4 Known to fail| |12.1.0 Blocks|24639 | Known to work| |11.1.0 Summary|Binding a reference to an |[12/13/14 Regression] |uninitialized data member |Binding a reference to an |should not cause |uninitialized data member |-Wuninitialized |should not cause | |-Wuninitialized --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This warning is from the front-end: else if (cp_tree_equal (TREE_OPERAND (init, 0), current_class_ref) && uninitialized->contains (field)) { if (TYPE_REF_P (TREE_TYPE (field))) warning_at (EXPR_LOCATION (init), OPT_Wuninitialized, "reference %qD is not yet bound to a value when used " "here", field); else if (!INDIRECT_TYPE_P (type) || is_this_parameter (d->member)) warning_at (EXPR_LOCATION (init), OPT_Wuninitialized, "member %qD is used uninitialized", field); *walk_subtrees = false; } Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 [Bug 24639] [meta-bug] bug to track all Wuninitialized issues
next prev parent reply other threads:[~2024-02-19 5:26 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 ` pinskia at gcc dot gnu.org [this message] 2024-02-19 5:26 ` [Bug c++/113987] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2024-02-19 5:32 ` pinskia at gcc dot gnu.org 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-R54Ybnc5Yv@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).