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/65832] New: Inefficient vector construction Date: Tue, 21 Apr 2015 13:56:00 -0000 [thread overview] Message-ID: <bug-65832-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65832 Bug ID: 65832 Summary: Inefficient vector construction Product: gcc Version: 6.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target: x86_64-*-*, i?86-*-* typedef int v4si __attribute__((vector_size(16))); v4si foo (int i, int j, int k, int l) { return (v4si) { i, j, k, l }; } produces movl %edx, -12(%rsp) movd -12(%rsp), %xmm1 movl %ecx, -12(%rsp) movd -12(%rsp), %xmm2 movl %edi, -12(%rsp) movd -12(%rsp), %xmm0 movl %esi, -12(%rsp) movd -12(%rsp), %xmm3 punpckldq %xmm2, %xmm1 punpckldq %xmm3, %xmm0 punpcklqdq %xmm1, %xmm0 ret as we spill everything to the stack we could as well use a vector load, thus something like movl %edx, -12(%rsp) movl %ecx, -16(%rsp) movl %edi, -20(%rsp) movl %esi, -24(%rsp) movdqu -12(%rsp), %xmm0 ret
next reply other threads:[~2015-04-21 13:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-21 13:56 rguenth at gcc dot gnu.org [this message] 2015-04-21 14:03 ` [Bug target/65832] " rguenth at gcc dot gnu.org 2015-04-21 14:11 ` rguenth at gcc dot gnu.org 2015-04-28 8:51 ` rguenth at gcc dot gnu.org 2015-04-28 8:55 ` rguenth at gcc dot gnu.org 2015-05-22 12:15 ` rguenth at gcc dot gnu.org 2015-06-01 10:30 ` rguenth at gcc dot gnu.org 2020-06-24 20:45 ` [Bug middle-end/65832] " gabravier at gmail dot com
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-65832-4@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).