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/96135] [9/10/11 regression] bswap not detected by bswap pass, unexpected results between optimization levels Date: Fri, 10 Jul 2020 07:19:35 +0000 [thread overview] Message-ID: <bug-96135-4-logadz1s97@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96135-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96135 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2020-07-10 Keywords| |missed-optimization Target Milestone|--- |9.4 Ever confirmed|0 |1 Priority|P3 |P2 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- The bswap pass doesn't handle these patterns at all (it doesn't look at stores). What does handle this case is store-merging which - on trunk - figures bswap in f() but not in g() likely because of the BIT_FIELD_REF -> cast folding which makes the stores appear inhomogenous: _3 = VIEW_CONVERT_EXPR<long long int>(x_2(D)); _4 = BIT_FIELD_REF <x_2(D), 8, 56>; v.c[0] = _4; ... _11 = (char) _3; v.c[7] = _11; store-merging already handles the cast vs. BIT_FIELD_REF case for f() but it appearantly doesn't consider to look through a VIEW_CONVERT. With -O3 we vectorize this in an inconvenient way and fully elide the store so store-merging isn't the correct pass to handle this: _3 = BIT_FIELD_REF <i_2(D), 8, 56>; _4 = BIT_FIELD_REF <i_2(D), 8, 48>; _5 = BIT_FIELD_REF <i_2(D), 8, 40>; _6 = BIT_FIELD_REF <i_2(D), 8, 32>; _7 = BIT_FIELD_REF <i_2(D), 8, 24>; _8 = BIT_FIELD_REF <i_2(D), 8, 16>; _9 = BIT_FIELD_REF <i_2(D), 8, 8>; _10 = (char) i_2(D); _21 = {_3, _4, _5, _6, _7, _8, _9, _10}; _18 = VIEW_CONVERT_EXPR<long long int>(_21); v ={v} {CLOBBER}; return _18; the vectorizer is also confused about BIT_FIELD_REF vs. cast here (I repeatedly thought of removing that simplification ... but the user could have written it as well :/). And it would look for a vector function argument but that's something that could be fixed. The above is all for GCC 10. GCC 8 possibly was lucky and did not have that BIT_FIELD_REF -> cast simplification.
next prev parent reply other threads:[~2020-07-10 7:19 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-09 14:01 [Bug tree-optimization/96135] New: " tobi at gcc dot gnu.org 2020-07-10 7:19 ` rguenth at gcc dot gnu.org [this message] 2021-03-11 9:07 ` [Bug tree-optimization/96135] " rguenth at gcc dot gnu.org 2021-03-31 9:13 ` rguenth at gcc dot gnu.org 2021-06-01 8:18 ` [Bug tree-optimization/96135] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-09-08 10:48 ` pinskia at gcc dot gnu.org 2021-09-08 10:58 ` pinskia at gcc dot gnu.org 2022-05-27 9:43 ` [Bug tree-optimization/96135] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 10:37 ` [Bug tree-optimization/96135] [11/12/13/14 " 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-96135-4-logadz1s97@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).