public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/48941] [arm gcc] NEON: Stack pointer operations performed even tho stack is not accessed at all in function.
Date: Thu, 12 May 2011 07:26:00 -0000 [thread overview]
Message-ID: <bug-48941-4-M0yuTWK1lg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48941-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48941
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|arm-elf |arm-elf, arm-eabi
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.05.12 07:07:51
CC| |ramana at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2011-05-12 07:07:51 UTC ---
Occurs with trunk as well.
This is what I see with "GCC: (GNU) 4.7.0 20110413 (experimental) [trunk
revision 172363
str fp, [sp, #-4]!
add fp, sp, #0
sub sp, sp, #20
vldmia r0, {d20-d21}
vmov q11, q10 @ v4sf
sub sp, sp, #48
add r3, sp, #15
bic r3, r3, #15
vzip.32 q10, q11
vstr d22, [r3, #16]
vstr d23, [r3, #24]
vstmia r3, {d20-d21}
vldmia r1, {d18-d19}
vmov q8, q9 @ v4sf
vmov d24, d21
vzip.32 q9, q8
vstr d16, [r3, #16]
vstr d17, [r3, #24]
vstmia r3, {d18-d19}
vmov d26, d22
vmov d25, d16
vmov d23, d18
vmul.f32 d16, d24, d25
vmul.f32 d22, d26, d23
vmov d18, d19
vmul.f32 d17, d20, d18
vmls.f32 d16, d26, d18
vmls.f32 d22, d20, d25
vmls.f32 d17, d24, d23
vuzp.32 d16, d22
vmov d18, d16
vmov d19, d17
vmov r0, r1, d18 @ v4sf
vmov r2, r3, d19
add sp, fp, #0
ldmfd sp!, {fp}
bx lr
next prev parent reply other threads:[~2011-05-12 7:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 3:13 [Bug target/48941] New: " julien at cayzac dot name
2011-05-12 7:26 ` ramana at gcc dot gnu.org [this message]
2011-05-12 7:39 ` [Bug target/48941] " rsandifo at gcc dot gnu.org
2011-05-12 9:22 ` rsandifo at gcc dot gnu.org
2011-05-16 9:07 ` rearnsha at gcc dot gnu.org
2011-06-02 13:41 ` rsandifo at gcc dot gnu.org
2011-11-24 11:35 ` rearnsha at gcc dot gnu.org
2012-01-18 12:06 ` rsandifo at gcc dot gnu.org
2012-01-27 14:40 ` eric.batut at allegorithmic dot com
2012-01-27 17:12 ` ramana at gcc dot gnu.org
2012-05-02 6:29 ` ramana at gcc dot gnu.org
2012-05-02 6:52 ` ramana at gcc dot gnu.org
2012-05-22 14:40 ` ramana at gcc dot gnu.org
2012-07-05 16:57 ` ramana at gcc dot gnu.org
2012-07-05 17:02 ` ramana 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-48941-4-M0yuTWK1lg@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: link
Be 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).