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++/111123] Warning about "used uninitialized" member shown or hidden randomly
Date: Thu, 24 Aug 2023 13:11:58 +0000	[thread overview]
Message-ID: <bug-111123-4-jOuwDlQ60v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111123-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111123

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:abf915193fbf725bb359e6936e10dcc282eb94cc

commit r14-3460-gabf915193fbf725bb359e6936e10dcc282eb94cc
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Aug 24 09:32:54 2023 +0200

    tree-optimization/111123 - indirect clobbers thrown away too early

    The testcase in the PR shows that late uninit diagnostic relies
    on indirect clobbers in CTORs but we throw those away in the fab
    pass which is too early.  The reasoning was they were supposed
    to keep SSA names live but that's no longer the case since DCE
    doesn't treat them as keeping SSA uses live.

    The following instead removes them before out-of-SSA coalescing
    which is the thing that's still affected by them.

            PR tree-optimization/111123
            * tree-ssa-ccp.cc (pass_fold_builtins::execute): Do not
            remove indirect clobbers here ...
            * tree-outof-ssa.cc (rewrite_out_of_ssa): ... but here.
            (remove_indirect_clobbers): New function.

            * g++.dg/warn/Wuninitialized-pr111123-1.C: New testcase.

  parent reply	other threads:[~2023-08-24 13:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 19:57 [Bug c++/111123] New: " agriff at tin dot it
2023-08-23 20:12 ` [Bug c++/111123] " agriff at tin dot it
2023-08-24  6:52 ` rguenth at gcc dot gnu.org
2023-08-24  7:14 ` rguenth at gcc dot gnu.org
2023-08-24  7:36 ` rguenth at gcc dot gnu.org
2023-08-24 13:11 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-24 13:13 ` 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-111123-4-jOuwDlQ60v@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).