public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95058] [11 regression] vector test case failures starting with r11-205 Date: Tue, 12 May 2020 12:28:52 +0000 [thread overview] Message-ID: <bug-95058-4-OLrL1Bmq3T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95058-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95058 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Last reconfirmed| |2020-05-12 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- OK, so for non 7 BE we end up not vectorizing because it doesn't look profitable which IMHO is good. It would be nice to also see dumps before the respective rev. because in theory (well...) the cost computation should be the same. Ah! OK, so we now have 0x10002001470 _1 1 times vec_construct costs 2 in prologue 0x10002001470 _1 1 times vec_construct costs 2 in prologue 0x10002001470 _1 2 times vector_store costs 2 in body 0x10001ecfcc0 _1 1 times scalar_store costs 1 in body 0x10001ecfcc0 _2 1 times scalar_store costs 1 in body 0x10001ecfcc0 _3 1 times scalar_store costs 1 in body 0x10001ecfcc0 _4 1 times scalar_store costs 1 in body that is, the SLP graph has the expected cost. Originally we likely had costed against 4 scalar stores and 4 scalar loads (but the scalar loads will still be there). On x86_64 we get 0x3975280 _1 1 times vec_construct costs 8 in prologue 0x3975280 _1 1 times vec_construct costs 8 in prologue 0x3975280 _1 2 times vector_store costs 24 in body 0x3942cb0 _1 1 times scalar_store costs 12 in body 0x3942cb0 _2 1 times scalar_store costs 12 in body 0x3942cb0 _3 1 times scalar_store costs 12 in body 0x3942cb0 _4 1 times scalar_store costs 12 in body so it's still profitable there. Note I suggest to leave the FAILs in place for now since in my dev tree I see the vec_construct gone again so it would start passing again on ppc as well. Sorry for the intermediate breakage.
next prev parent reply other threads:[~2020-05-12 12:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 13:01 [Bug other/95058] New: " seurer at linux dot vnet.ibm.com 2020-05-11 13:04 ` [Bug tree-optimization/95058] " rguenth at gcc dot gnu.org 2020-05-11 15:17 ` seurer at linux dot vnet.ibm.com 2020-05-11 15:19 ` seurer at linux dot vnet.ibm.com 2020-05-11 15:23 ` seurer at linux dot vnet.ibm.com 2020-05-11 15:23 ` seurer at linux dot vnet.ibm.com 2020-05-12 12:28 ` rguenth at gcc dot gnu.org [this message] 2020-05-25 14:04 ` rguenth at gcc dot gnu.org 2020-05-25 14:09 ` rguenth at gcc dot gnu.org 2020-05-26 15:33 ` seurer at linux dot vnet.ibm.com 2020-06-03 2:49 ` seurer at linux dot vnet.ibm.com 2020-07-08 6:54 ` 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-95058-4-OLrL1Bmq3T@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: linkBe 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).