public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/42321] NEON/VFP registers from inline assembly clobber list are saved/restored incorrectly
Date: Thu, 14 Jan 2010 16:21:00 -0000 [thread overview]
Message-ID: <20100114162104.14869.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42321-14457@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ramana at gcc dot gnu dot org 2010-01-14 16:21 -------
I took a cursory look at this case . This looks like a bug in the
backend specifically in arm_output_epilogue where the epilogue code
isn't designed to cope for restoring disjoint sets of registers from
the stack when the frame pointer is eliminated.
The epilogue code for restoring these registers would work fine in the
case where
a. The registers to be restored are in a single sequence for load
multiple irrespective of whether the frame pointer is used or not.
b. If the function ends up using a frame_pointer.
We need a separate case for when the frame pointer is not required and
one has more than one sequence to restore.
--
ramana at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Known to fail| |4.4.2 4.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42321
next prev parent reply other threads:[~2010-01-14 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 14:34 [Bug inline-asm/42321] New: " siarhei dot siamashka at gmail dot com
2009-12-07 14:42 ` [Bug inline-asm/42321] " siarhei dot siamashka at gmail dot com
2009-12-07 15:52 ` ramana at gcc dot gnu dot org
2009-12-07 15:56 ` rearnsha at gcc dot gnu dot org
2009-12-09 16:55 ` ramana at gcc dot gnu dot org
2010-01-14 16:21 ` ramana at gcc dot gnu dot org [this message]
2010-03-21 15:59 ` rearnsha at gcc dot gnu dot org
2010-03-21 20:27 ` rearnsha at gcc dot gnu dot org
2010-03-21 20:30 ` [Bug target/42321] " rearnsha 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=20100114162104.14869.qmail@sourceware.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: 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).