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/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang Date: Wed, 13 Jan 2021 13:51:25 +0000 [thread overview] Message-ID: <bug-92645-4-lrQaU5WGsV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645 --- Comment #26 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:285fa338b06b804e72997c4d876ecf08a9c083af commit r11-6649-g285fa338b06b804e72997c4d876ecf08a9c083af Author: Richard Biener <rguenther@suse.de> Date: Wed Jan 13 13:48:31 2021 +0100 tree-optimization/92645 - avoid harmful early BIT_FIELD_REF canonicalization This avoids canonicalizing BIT_FIELD_REF <T1> (a, <sz>, 0) to (T1)a on integer typed a. This confuses the vectorizer SLP matching. With this delayed to after vector lowering the testcase in PR92645 from Skia is now finally optimized to reasonable assembly. 2021-01-13 Richard Biener <rguenther@suse.de> PR tree-optimization/92645 * match.pd (BIT_FIELD_REF to conversion): Delay canonicalization until after vector lowering. * gcc.target/i386/pr92645-7.c: New testcase. * gcc.dg/tree-ssa/ssa-fre-54.c: Adjust. * gcc.dg/pr69047.c: Likewise.
next prev parent reply other threads:[~2021-01-13 13:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92645-4@http.gcc.gnu.org/bugzilla/> 2020-04-23 13:26 ` rguenth at gcc dot gnu.org 2021-01-13 10:45 ` rguenth at gcc dot gnu.org 2021-01-13 12:38 ` cvs-commit at gcc dot gnu.org 2021-01-13 13:51 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-13 13:51 ` rguenth at gcc dot gnu.org 2023-05-22 20:51 ` pinskia 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-92645-4-lrQaU5WGsV@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).