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 target/109747] [12/13/14 Regression] SLP cost of constructors is off
Date: Tue, 23 May 2023 16:59:16 +0000	[thread overview]
Message-ID: <bug-109747-4-32Sn5nTs9M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109747-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:b6b8870ec585947a03a797f9037d02380316e235

commit r14-1139-gb6b8870ec585947a03a797f9037d02380316e235
Author: Richard Biener <rguenther@suse.de>
Date:   Tue May 23 15:03:00 2023 +0200

    tree-optimization/109747 - SLP cost of CTORs

    The x86 backend looks at the SLP node passed to the add_stmt_cost
    hook when costing vec_construct, looking for elements that require
    a move from a GPR to a vector register and cost that.  But since
    vect_prologue_cost_for_slp decomposes the cost for an external
    SLP node into individual pieces this cost gets applied N times
    without a chance for the backend to know it's just dealing with
    a part of the SLP node.  Just looking at a part is also not perfect
    since the GPR to XMM move cost applies only once per distinct
    element so handling the whole SLP node one more correctly reflects
    cost (albeit without considering other external SLP nodes).

    The following addresses the issue by passing down the SLP node
    only for one piece and nullptr for the rest.  The x86 backend
    is currently the only one looking at it.

    In the future the cost of external elements is something to deal
    with globally but that would require the full SLP tree be available
    to costing.

    It's difficult to write a testcase, at the tipping point not
    vectorizing is better so I'll followup with x86 specific adjustments
    and will see to add a testcase later.

            PR tree-optimization/109747
            * tree-vect-slp.cc (vect_prologue_cost_for_slp): Pass down
            the SLP node only once to the cost hook.

  parent reply	other threads:[~2023-05-23 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 11:56 [Bug target/109747] New: " rguenth at gcc dot gnu.org
2023-05-05 12:02 ` [Bug target/109747] " rguenth at gcc dot gnu.org
2023-05-08 12:27 ` rguenth at gcc dot gnu.org
2023-05-09 11:05 ` rguenth at gcc dot gnu.org
2023-05-23 16:59 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-23 17:00 ` [Bug target/109747] [12/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-109747-4-32Sn5nTs9M@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).