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/92706] SRA confuses FRE
Date: Wed, 16 Nov 2022 12:13:35 +0000	[thread overview]
Message-ID: <bug-92706-4-OYTCrZWyib@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92706-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Martin Jambor
<jamborm@gcc.gnu.org>:

https://gcc.gnu.org/g:985a8962712a56d1c9418cf05e1761f8bd20cf8f

commit r12-8913-g985a8962712a56d1c9418cf05e1761f8bd20cf8f
Author: Martin Jambor <mjambor@suse.cz>
Date:   Wed Nov 16 13:11:27 2022 +0100

    SRA: Limit replacement creation for accesses propagated from LHSs

    PR 107206 is fallout from the fix to PR 92706 where we started
    propagating accesses across assignments also from LHS to RHS of
    assignments so that we would not do harmful total scalarization of the
    aggregates on the RHS.

    But this can lead to new scalarization of these aggregates and in the
    testcase of PR 107206 these can appear in superfluous uses of
    un-initialized values and spurious warnings.

    Fixed by making sure the the accesses created by propagation in this
    direction are only used as a basis for replacements when the structure
    would be totally scalarized anyway.

    gcc/ChangeLog:

    2022-10-18  Martin Jambor  <mjambor@suse.cz>

            PR tree-optimization/107206
            * tree-sra.cc (struct access): New field
grp_result_of_prop_from_lhs.
            (analyze_access_subtree): Do not create replacements for accesses
with
            this flag when not toally scalarizing.
            (propagate_subaccesses_from_lhs): Set the new flag.

    gcc/testsuite/ChangeLog:

    2022-10-18  Martin Jambor  <mjambor@suse.cz>

            PR tree-optimization/107206
            * g++.dg/tree-ssa/pr107206.C: New test.

    (cherry picked from commit f6c168f8c06047bfaa3005e570126831b8855dcc)

      parent reply	other threads:[~2022-11-16 12:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92706-4@http.gcc.gnu.org/bugzilla/>
2022-10-19 12:59 ` cvs-commit at gcc dot gnu.org
2022-11-16 12:13 ` cvs-commit at gcc dot gnu.org [this message]

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-92706-4-OYTCrZWyib@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).