From: Shuo Wang <wangshuo47@huawei.com>
To: <libc-alpha@sourceware.org>, <szabolcs.nagy@arm.com>,
<carlos@redhat.com>
Cc: <hushiyuan@huawei.com>, <liqingqing3@huawei.com>
Subject: [PATCH] aarch64: fix stack missing after sp is updated
Date: Tue, 5 Jan 2021 10:02:34 +0800 [thread overview]
Message-ID: <20210105020234.1032-1-wangshuo47@huawei.com> (raw)
Dear Szabolcs,
Thanks for your reply. 'aarch64: ' prefix has been added to subject,
and signature has been replaced by Co-authored-by. This is the new patch:
https://sourceware.org/pipermail/libc-alpha/2021-January/121328.html
Best regards,
Shuo
>please add 'aarch64: ' prefix to the subject.
>
>i think it's enough to have the before the fix gdb
>session in the commit message.
>
>with those changes this is ok to commit.
>(if you don't have commit rights then send
>an updated patch and i'll commit it for you)
>
>> ---
>> sysdeps/aarch64/dl-tlsdesc.S | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/sysdeps/aarch64/dl-tlsdesc.S b/sysdeps/aarch64/dl-tlsdesc.S
>> index 0046d29f9b..425e45a50f 100644
>> --- a/sysdeps/aarch64/dl-tlsdesc.S
>> +++ b/sysdeps/aarch64/dl-tlsdesc.S
>> @@ -150,8 +150,8 @@ _dl_tlsdesc_dynamic:
>> /* Save just enough registers to support fast path, if we fall
>> into slow path we will save additional registers. */
>> stp x1, x2, [sp, #-32]!
>> - stp x3, x4, [sp, #16]
>> cfi_adjust_cfa_offset (32)
>> + stp x3, x4, [sp, #16]
>> cfi_rel_offset (x1, 0)
>> cfi_rel_offset (x2, 8)
>> cfi_rel_offset (x3, 16)
>> --
>> 2.23.0
>>
next reply other threads:[~2021-01-05 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 2:02 Shuo Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-05 10:39 Shuo Wang
2021-01-05 11:21 ` Florian Weimer
2021-01-05 2:22 Shuo Wang
2021-01-05 1:59 Shuo Wang
2021-01-04 12:42 Shuo Wang
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=20210105020234.1032-1-wangshuo47@huawei.com \
--to=wangshuo47@huawei.com \
--cc=carlos@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=liqingqing3@huawei.com \
--cc=szabolcs.nagy@arm.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).