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 target/96166] [10/11 Regression] -O3/-ftree-slp-vectorize turns ROL into a mess Date: Mon, 13 Jul 2020 08:05:32 +0000 [thread overview] Message-ID: <bug-96166-4-YUpCA3NWP7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96166-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96166 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |10.2 Blocks| |53947 Keywords| |missed-optimization Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2020-07-13 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. 0x3c02500 _10 1 times vector_store costs 12 in body 0x3c02500 <unknown> 1 times vec_construct costs 8 in prologue 0x3a3e900 _10 1 times scalar_store costs 12 in body 0x3a3e900 _9 1 times scalar_store costs 12 in body t.i:14:1: note: Cost model analysis: Vector inside of basic block cost: 12 Vector prologue cost: 8 Vector epilogue cost: 0 Scalar cost of basic block: 24 t.i:14:1: note: Basic block will be vectorized using SLP and we end up with <bb 2> [local count: 1073741824]: _3 = MEM <long unsigned int> [(char * {ref-all})x_2(D)]; _9 = (int) _3; _10 = BIT_FIELD_REF <_3, 32, 32>; _11 = {_10, _9}; _7 = VIEW_CONVERT_EXPR<long unsigned int>(_11); MEM <long unsigned int> [(char * {ref-all})x_2(D)] = _7; the IL we feed into the vectorizer and the earlier bswap pass is _3 = MEM <long unsigned int> [(char * {ref-all})x_2(D)]; _9 = (int) _3; _10 = BIT_FIELD_REF <_3, 32, 32>; y = _10; MEM[(int &)&y + 4] = _9; _4 = MEM <long unsigned int> [(char * {ref-all})&y]; MEM <long unsigned int> [(char * {ref-all})x_2(D)] = _4; I guess fixing the vectorizer to handle the "grouped load" would eventually allow fixing this. I don't think there's anything to do from the costing side... Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations
next prev parent reply other threads:[~2020-07-13 8:05 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-11 16:01 [Bug tree-optimization/96166] New: " nok.raven at gmail dot com 2020-07-13 8:05 ` rguenth at gcc dot gnu.org [this message] 2020-07-23 6:51 ` [Bug target/96166] " rguenth at gcc dot gnu.org 2020-10-12 12:47 ` rguenth at gcc dot gnu.org 2021-02-11 15:00 ` jakub at gcc dot gnu.org 2021-02-12 10:11 ` jakub at gcc dot gnu.org 2021-02-12 11:18 ` jakub at gcc dot gnu.org 2021-02-12 12:17 ` pinskia at gcc dot gnu.org 2021-02-12 12:21 ` jakub at gcc dot gnu.org 2021-02-12 13:53 ` jakub at gcc dot gnu.org 2021-02-12 14:03 ` rguenth at gcc dot gnu.org 2021-02-12 14:40 ` jakub at gcc dot gnu.org 2021-02-13 9:33 ` cvs-commit at gcc dot gnu.org 2021-02-13 9:34 ` [Bug target/96166] [10 " jakub at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 8:55 ` 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-96166-4-YUpCA3NWP7@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).