public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/24073] New: (vector float){a, b, 0, 0} code gen is not good Date: Tue, 27 Sep 2005 04:06:00 -0000 [thread overview] Message-ID: <20050927040602.24073.pinskia@gcc.gnu.org> (raw) Take the following example: #define vector __attribute__((vector_size(16))) float a; float b; vector float f(void) { return (vector float){ a, b, 0.0, 0.0}; } --- Currently we get: subl $12, %esp movss _b, %xmm0 movss _a, %xmm1 unpcklps %xmm0, %xmm1 movaps %xmm1, %xmm0 xorl %eax, %eax xorl %edx, %edx movl %eax, (%esp) movl %edx, 4(%esp) xorps %xmm1, %xmm1 movlhps %xmm1, %xmm0 addl $12, %esp ------ We should be able to produce: movss _b, %xmm0 movss _a, %xmm1 shufps 60, /*[0, 3, 3, 0]*/, %xmm1, %xmm0 // _a, 0, 0, _b shufps 201, /*[3, 0, 2, 1]*/, %xmm0, %xmm0 // _a, _b, 0, 0 This is from Nathan Begeman. -- Summary: (vector float){a, b, 0, 0} code gen is not good Product: gcc Version: 4.1.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: minor Priority: P2 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24073
next reply other threads:[~2005-09-27 4:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-09-27 4:06 pinskia at gcc dot gnu dot org [this message] 2005-09-27 4:06 ` [Bug target/24073] " pinskia at gcc dot gnu dot org 2005-09-27 4:22 ` pinskia at gcc dot gnu dot org 2005-09-27 5:09 ` pinskia at gcc dot gnu dot org 2005-09-27 5:51 ` belyshev at depni dot sinp dot msu dot ru 2005-09-27 11:19 ` uros at kss-loka dot si 2005-09-27 11:41 ` uros at kss-loka dot si 2005-09-27 14:34 ` pinskia at gcc dot gnu dot 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=20050927040602.24073.pinskia@gcc.gnu.org \ --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).