From: Jie Zhang <jie@codesourcery.com>
To: Paul Brook <paul@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [ARM] Fix prologue and epilogue for interrupt function
Date: Mon, 12 Jul 2010 14:06:00 -0000 [thread overview]
Message-ID: <4C3B2147.908@codesourcery.com> (raw)
In-Reply-To: <4C3B1B66.4040402@codesourcery.com>
On 07/12/2010 09:40 PM, Jie Zhang wrote:
> On 07/07/2010 09:49 PM, Paul Brook wrote:
>>> ARM GCC will save r3 to the stack when it tries to align the stack to
>>> double-word. But it can only do so when r3 will not be saved. Otherwise
>>> there will be inconsistent information about how many registers will be
>>> saved and how much the stack will be adjusted. This patch fixes it.
>>>
>>> Tested on arm-none-eabi. No regressions are found. Is it OK?
>>
>> Your test fails for Thumb multilibs.
>>
>> Other than that, ok.
>>
> Here is the updated patch, with test cases updated. The method used in
> the tests to make them work with thumb is Paul's idea. I will commit on
> trunk and 4.5 branch soon.
>
Done.
--
Jie Zhang
CodeSourcery
prev parent reply other threads:[~2010-07-12 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 5:47 Jie Zhang
2010-07-07 13:50 ` Paul Brook
2010-07-12 13:41 ` Jie Zhang
2010-07-12 14:06 ` Jie Zhang [this message]
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=4C3B2147.908@codesourcery.com \
--to=jie@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul@codesourcery.com \
/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).