From: Yufeng Zhang <Yufeng.Zhang@arm.com>
To: libffi-discuss@sourceware.org
Cc: green@moxielogic.com, Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PING^3] Re: [PATCH, AArch64] Fix Call Frame Information in ffi_closure_SYSV
Date: Thu, 20 Feb 2014 14:59:00 -0000 [thread overview]
Message-ID: <5306184F.1020300@arm.com> (raw)
In-Reply-To: <52FBB8AB.5050305@arm.com>
Ping^3~~~
Is there a way in getting attention from libffi maintainers? I really
would like to see the patch made into gcc before the stage 4 closes.
Thanks,
Yufeng
On 02/12/14 18:08, Yufeng Zhang wrote:
> Ping^2~~
>
> Thanks,
> Yufeng
>
> On 01/14/14 12:10, Yufeng Zhang wrote:
>> Ping~
>>
>> Originally posted it:
>> http://sourceware.org/ml/libffi-discuss/2013/msg00240.html
>>
>> Thanks,
>> Yufeng
>>
>> On 12/23/13 18:30, Yufeng Zhang wrote:
>>> Hi,
>>>
>>> This patch fixes a bug in ./src/aarch64/sysv.S:ffi_closure_SYSV where
>>> stack unwinding information was not generated correctly.
>>>
>>> OK for the mainline?
>>>
>>> Thanks,
>>> Yufeng
>>>
>>> 2013-12-23 Yufeng Zhang<yufeng.zhang@arm.com>
>>>
>>> * src/aarch64/sysv.S (ffi_closure_SYSV): Use x29 as the
>>> main CFA reg; update cfi_rel_offset.
>>
>>
>>
>
>
>
next prev parent reply other threads:[~2014-02-20 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 18:30 Yufeng Zhang
2014-01-06 12:36 ` Marcus Shawcroft
2014-01-14 12:10 ` [PING] " Yufeng Zhang
2014-02-12 18:08 ` [PING^2] " Yufeng Zhang
2014-02-20 14:59 ` Yufeng Zhang [this message]
2014-02-28 5:28 ` [PING] " Anthony Green
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=5306184F.1020300@arm.com \
--to=yufeng.zhang@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@moxielogic.com \
--cc=libffi-discuss@sourceware.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).