From: Sudakshina Das <Sudi.Das@arm.com>
To: "nickc@redhat.com" <nickc@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Cc: nd <nd@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH, BFD, AArch64, x86] Improve warning for --force-bti.
Date: Thu, 21 Mar 2019 16:24:00 -0000 [thread overview]
Message-ID: <d0a68dd5-afcb-0888-61ad-e4ad7e96fc2e@arm.com> (raw)
In-Reply-To: <fcff06e3-5c32-fcef-b22d-f39e22d51b0a@redhat.com>
Hi Nick
On 21/03/2019 15:14, Nick Clifton wrote:
> Hi Sudi,
>
>> *** bfd/ChangeLog ***
>>
>> 2019-xx-xx Sudakshina Das <sudi.das@arm.com>
>>
>> * elf-bfd.h (struct elf_backend_data): Add argument to
>> merge_gnu_properties.
>> * elf-properties.c (elf_merge_gnu_properties): Add argument to
>> itself and while calling bed->merge_gnu_properties.
>> (elf_merge_gnu_property_list): Update the calls for
>> elf_merge_gnu_properties.
>> * elfnn-aarch64.c (elfNN_aarch64_merge_gnu_properties): Update handling
>> of --force-bti warning and add argument.
>> * elfxx-aarch64.c (_bfd_aarch64_elf_link_setup_gnu_properties): Add
>> warning.
>> * elfxx-x86.c (_bfd_x86_elf_merge_gnu_properties): Add argument.
>> * elfxx-x86.h (_bfd_x86_elf_merge_gnu_properties): Likewise in
>> declaration.
>>
>> *** ld/ChangeLog ***
>>
>> 2019-xx-xx Sudakshina Das <sudi.das@arm.com>
>>
>> * testsuite/ld-aarch64/aarch64-elf.exp: Add new test.
>> * testsuite/ld-aarch64/bti-plt-1.s: Add .ifdef for PAC note section.
>> * testsuite/ld-aarch64/bti-plt-6.d: Update warning.
>> * testsuite/ld-aarch64/bti-plt-7.d: Likewise.
>> * testsuite/ld-aarch64/bti-warn.d: New test.
>
> Approved - please apply.
Thanks for the approval. Committed as
4e5391148d51c58785aad637f1a92d47b91b3ae6
Sudi
>
> Cheers
> Nick
>
>
next prev parent reply other threads:[~2019-03-21 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 13:30 Sudakshina Das
2019-03-21 15:14 ` Nick Clifton
2019-03-21 16:24 ` Sudakshina Das [this message]
2019-03-21 22:57 ` H.J. Lu
2019-04-01 19:27 ` H.J. Lu
2019-04-02 9:05 ` Sudakshina Das
2019-04-02 12:32 ` H.J. Lu
2019-04-03 14:36 ` Sudakshina Das
2019-04-12 14:42 ` Sudakshina Das
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=d0a68dd5-afcb-0888-61ad-e4ad7e96fc2e@arm.com \
--to=sudi.das@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=nd@arm.com \
--cc=nickc@redhat.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).