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/33315] stores not commoned by sinking
Date: Fri, 15 May 2020 06:56:33 +0000	[thread overview]
Message-ID: <bug-33315-4-DLjhJSsX3K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-33315-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 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:84935c9822183ce403bb361c5f405711b9a808c6

commit r11-408-g84935c9822183ce403bb361c5f405711b9a808c6
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Apr 15 12:09:01 2020 +0200

    tree-optimization/33315 - common stores during sinking

    This implements commoning of stores to a common successor in
    a simple ad-hoc way.  I've decided to put it into the code sinking
    pass since, well, it sinks stores.  It's still separate since
    it does not really sink code into less executed places.

    It's ad-hoc since it does not perform any dataflow or alias analysis
    but simply only considers trailing stores in a block, iteratively
    though.  If the stores are from different values a PHI node is
    inserted to merge them.  gcc.dg/tree-ssa/split-path-7.c shows
    that path splitting will eventually undo this very transform,
    I've decided to not bother with it and simply disable sinking for
    the particular testcase.

    Doing this transform is good for code size when the stores are
    from constants, once we have to insert PHIs the situation becomes
    less clear but it's a transform we do elsewhere as well
    (cselim for one), and reversing the transform should be easy.

    2020-05-15  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/33315
            * tree-ssa-sink.c: Include tree-eh.h.
            (sink_stats): Add commoned member.
            (sink_common_stores_to_bb): New function implementing store
            commoning by sinking to the successor.
            (sink_code_in_bb): Call it, pass down TODO_cleanup_cfg returned.
            (pass_sink_code::execute): Likewise.  Record commoned stores
            in statistics.

            * gcc.dg/tree-ssa/ssa-sink-13.c: New testcase.
            * gcc.dg/tree-ssa/ssa-sink-14.c: Likewise.
            * gcc.dg/tree-ssa/split-path-7.c: Disable sinking.

  parent reply	other threads:[~2020-05-15  6:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-33315-4@http.gcc.gnu.org/bugzilla/>
2012-02-04  2:34 ` [Bug middle-end/33315] If condition not getting eliminated pinskia at gcc dot gnu.org
2020-04-15 10:24 ` [Bug tree-optimization/33315] stores not commoned by sinking rguenth at gcc dot gnu.org
2020-04-15 18:17 ` rguenth at gcc dot gnu.org
2020-04-16 12:40 ` rguenth at gcc dot gnu.org
2020-05-15  6:56 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-15  6:57 ` 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-33315-4-DLjhJSsX3K@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).