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/106922] [12/13 Regression] Bogus uninitialized warning on boost::optional<<std::vector<std::string>>>, missed FRE
Date: Thu, 15 Sep 2022 12:36:07 +0000	[thread overview]
Message-ID: <bug-106922-4-zj6C8oCDVb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106922-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 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:5edf02ed2b6de024f83a023d046a6a18f645bc83

commit r13-2683-g5edf02ed2b6de024f83a023d046a6a18f645bc83
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Sep 15 13:33:23 2022 +0200

    tree-optimization/106922 - PRE and virtual operand translation

    PRE implicitely keeps virtual operands at the blocks incoming version
    but the explicit updating point during PHI translation fails to trigger
    when there are no PHIs at all in a block.  Later lazy updating then
    fails because of a too lose block check.  A similar issues plagues
    reference invalidation when checking the ANTIC_OUT to ANTIC_IN
    translation.  The following fixes both and makes the lazy updating
    work.

    The diagnostic testcase unfortunately requires boost so the
    testcase is the one I reduced for a missed optimization in PRE.
    The testcase fails with -m32 on x86_64 because we optimize too
    much before PRE which causes PRE to not trigger so we fail to
    eliminate a full redundancy.  I'm going to open a separate bug
    for this.  Hopefully the !lp64 selector is good enough.

            PR tree-optimization/106922
            * tree-ssa-pre.cc (translate_vuse_through_block): Only
            keep the VUSE if its def dominates PHIBLOCK.
            (prune_clobbered_mems): Rewrite logic so we check whether
            a value dies in a block when the VUSE def doesn't dominate it.

            * g++.dg/tree-ssa/pr106922.C: New testcase.

  parent reply	other threads:[~2022-09-15 12:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  8:18 [Bug tree-optimization/106922] New: [12 Regression] Bogus uninitialized warning on boost::optional<<std::vector<std::string>>> jan.zizka at nokia dot com
2022-09-13  9:13 ` [Bug tree-optimization/106922] [12/13 " rguenth at gcc dot gnu.org
2022-09-15  7:55 ` [Bug tree-optimization/106922] [12/13 Regression] Bogus uninitialized warning on boost::optional<<std::vector<std::string>>>, missed FRE rguenth at gcc dot gnu.org
2022-09-15  8:41 ` rguenth at gcc dot gnu.org
2022-09-15 11:26 ` rguenth at gcc dot gnu.org
2022-09-15 11:56 ` rguenth at gcc dot gnu.org
2022-09-15 11:57 ` rguenth at gcc dot gnu.org
2022-09-15 12:12 ` jan.zizka at nokia dot com
2022-09-15 12:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-15 12:38 ` [Bug tree-optimization/106922] [12 " rguenth at gcc dot gnu.org
2022-09-15 22:13 ` jan.zizka at nokia dot com
2022-09-19 14:16 ` rguenth at gcc dot gnu.org
2022-09-19 15:03 ` jan.zizka at nokia dot com
2022-09-21  6:55 ` rguenth at gcc dot gnu.org
2022-09-21 12:52 ` rguenth at gcc dot gnu.org
2022-09-22 11:10 ` cvs-commit at gcc dot gnu.org
2022-09-22 11:11 ` rguenth at gcc dot gnu.org
2022-09-23  7:48 ` cvs-commit at gcc dot gnu.org
2022-09-23 11:31 ` jan.zizka at nokia dot com
2022-09-23 11:59 ` rguenth at gcc dot gnu.org
2022-09-23 13:11 ` cvs-commit at gcc dot gnu.org
2022-09-23 13:14 ` rguenth at gcc dot gnu.org
2022-09-23 14:22 ` jan.zizka at nokia dot com
2022-10-11 12:06 ` cvs-commit at gcc dot gnu.org
2022-10-11 12:08 ` rguenth at gcc dot gnu.org
2022-10-11 13:13 ` jan.zizka at nokia dot com
2022-10-13  7:44 ` rguenther at suse dot de
2022-10-13 10:50 ` jan.zizka at nokia dot com
2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org
2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org
2022-10-17 13:10 ` cvs-commit at gcc dot gnu.org
2022-10-17 13:14 ` 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-106922-4-zj6C8oCDVb@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).