public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105965] x86: single-element vectors don't have scalar FMA insns used anymore Date: Tue, 14 Jun 2022 08:23:33 +0000 [thread overview] Message-ID: <bug-105965-4-78uLdEIx6i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105965-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105965 Hongtao.liu <crazylht at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crazylht at gmail dot com --- Comment #1 from Hongtao.liu <crazylht at gmail dot com> --- It looks like a regression since GCC9 typedef float v1sf __attribute__((vector_size(4))); v1sf foo43 (v1sf a, v1sf b, v1sf c) { return a * b + c; } gcc9 also don't generate vfmaddXXXss. pushq %rbp movq %rdi, %rax movq %rsp, %rbp andq $-32, %rsp vmovss 24(%rbp), %xmm0 vmulss 16(%rbp), %xmm0, %xmm0 vaddss 32(%rbp), %xmm0, %xmm0 vmovss %xmm0, -64(%rsp) movl -64(%rsp), %edx movl %edx, (%rdi) leave ret
next prev parent reply other threads:[~2022-06-14 8:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-14 6:31 [Bug target/105965] New: " jbeulich at suse dot com 2022-06-14 8:23 ` crazylht at gmail dot com [this message] 2022-06-14 8:40 ` [Bug target/105965] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2022-06-14 10:53 ` cvs-commit at gcc dot gnu.org 2022-06-14 10:53 ` [Bug target/105965] [10/11/12 " rguenth at gcc dot gnu.org 2022-06-21 1:52 ` [Bug tree-optimization/105965] " pinskia at gcc dot gnu.org 2022-06-21 6:59 ` rguenther at suse dot de 2022-06-28 10:49 ` jakub at gcc dot gnu.org 2022-07-19 11:38 ` cvs-commit at gcc dot gnu.org 2022-07-19 11:39 ` [Bug tree-optimization/105965] [10/11 " rguenth at gcc dot gnu.org 2023-07-07 10:43 ` [Bug tree-optimization/105965] [11 " 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-105965-4-78uLdEIx6i@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).