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 tree-optimization/111397] Spurious warning "'({anonymous})' is used uninitialized" when calling a __returns_twice__ function (-Wuninitialized -O2)
Date: Wed, 13 Sep 2023 08:22:37 +0000	[thread overview]
Message-ID: <bug-111397-4-drr2mmv2bo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111397-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:92ea12ea99fce546772a40b7bbc2ea850db9b1be

commit r14-3916-g92ea12ea99fce546772a40b7bbc2ea850db9b1be
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Sep 13 09:28:34 2023 +0200

    tree-optimization/111397 - missed copy propagation involving abnormal dest

    The following extends the previous enhancement to copy propagation
    involving abnormals.  We can easily replace abnormal uses by not
    abnormal uses and only need to preserve the abnormals in PHI arguments
    flowing in from abnormal edges.  This changes the may_propagate_copy
    argument indicating we are not propagating into a PHI node to indicate
    whether we know we are not propagating into a PHI argument from an
    abnormal PHI instead.

            PR tree-optimization/111397
            * tree-ssa-propagate.cc (may_propagate_copy): Change optional
            argument to specify whether the PHI destination doesn't flow in
            from an abnormal PHI.
            (propagate_value): Adjust.
            * tree-ssa-forwprop.cc (pass_forwprop::execute): Indicate abnormal
            PHI dest.
            * tree-ssa-sccvn.cc (eliminate_dom_walker::before_dom_children):
            Likewise.
            (process_bb): Likewise.

            * gcc.dg/uninit-pr111397.c: New testcase.

  parent reply	other threads:[~2023-09-13  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 20:31 [Bug tree-optimization/111397] New: " skiminki at gmail dot com
2023-09-12 21:15 ` [Bug tree-optimization/111397] " pinskia at gcc dot gnu.org
2023-09-13  7:28 ` rguenth at gcc dot gnu.org
2023-09-13  8:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-13  8:25 ` [Bug tree-optimization/111397] [12/13 Regression] " rguenth at gcc dot gnu.org
2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org
2024-06-20  9:13 ` [Bug tree-optimization/111397] [12 " 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-111397-4-drr2mmv2bo@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).