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/96654] Failure to optimize vectorized conversion to `int` with AVX Date: Tue, 25 Aug 2020 10:40:28 +0000 [thread overview] Message-ID: <bug-96654-4-9ybDXdrtIV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96654-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96654 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org Blocks| |53947 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- The pattern is exercised directly by BB vectorization only, loop vectorization still uses a fixed vector size. Still the assembly shows basically the same code when doing BB vectorization only: f: .LFB0: .cfi_startproc vmovupd (%rdi), %xmm1 vinsertf128 $0x1, 16(%rdi), %ymm1, %ymm0 vcvttpd2dqy %ymm0, %xmm0 vmovdqu %xmm0, (%rsi) vzeroupper ret this is probably because of some tuning (split unaligned loads, not using a memory operand for vcvttpd2dqy). With -O3 -fno-tree-loop-vectorize -march=core-avx2 I get f: .LFB0: .cfi_startproc vcvttpd2dqy (%rdi), %xmm0 vmovdqu %xmm0, (%rsi) ret Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations
prev parent reply other threads:[~2020-08-25 10:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-17 11:57 [Bug target/96654] New: " gabravier at gmail dot com 2020-08-17 19:04 ` [Bug tree-optimization/96654] " ubizjak at gmail dot com 2020-08-22 16:32 ` glisse at gcc dot gnu.org 2020-08-25 10:40 ` rguenth at gcc dot gnu.org [this message]
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-96654-4-9ybDXdrtIV@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).