From: Sudakshina Das <Sudi.Das@arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: James Greenhalgh <James.Greenhalgh@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
nd <nd@arm.com>, Richard Earnshaw <Richard.Earnshaw@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [PATCH, GCC, AARCH64, 5/6] Enable BTI : Add new pass for BTI.
Date: Thu, 10 Jan 2019 16:55:00 -0000 [thread overview]
Message-ID: <02937f59-56ad-0305-84e2-8406dd1ed47c@arm.com> (raw)
In-Reply-To: <CAKdteObNi=WdEBiA=tZvtemEWhnu3F1o42JMiSo5RCTmG2OEqA@mail.gmail.com>
Hi Christophe
On 10/01/19 15:46, Christophe Lyon wrote:
> On Wed, 9 Jan 2019 at 15:42, Sudakshina Das <Sudi.Das@arm.com> wrote:
>>
>> Hi
>>
>> On 20/12/18 16:40, Sudakshina Das wrote:
>>> Hi James
>>>
>>> On 19/12/18 3:40 PM, James Greenhalgh wrote:
>>>> On Fri, Dec 14, 2018 at 10:09:03AM -0600, Sudakshina Das wrote:
>>>>
>>>> <snip>
>>>>
>>>>> I have updated the patch according to our discussions offline.
>>>>> The md pattern is now split into 4 patterns and i have added a new
>>>>> test for the setjmp case along with some comments where missing.
>>>>
>>>> This is OK for trunk.
>>>>
>>>
>>> Thanks for the approvals. With this my series is ready to go in trunk. I
>>> will wait for Sam's options patch to go in trunk before I commit mine.
>>>
>>
>> Series is committed with a rebase without Sam Tebbs's 3rd patch for
>> B-Key addition as r267765 to r267770.
>>
>> Thanks
>> Sudi
>>
>
> Hi Sudi,
>
> I think the new bti-1.c test lacks
> /* { dg-require-effective-target lp64 } */
> as I see it failing when using -mabi=ilp32:
> cc1: sorry, unimplemented: return address signing is only supported
> for -mabi=lp64
>
Ah yes, I actually added code for exempting ilp32 in my configure patch
but missed it while adding test cases. Testing a patch right now.
Sudi
> Christophe
>
>>> Thanks
>>> Sudi
>>>
>>>> Thanks,
>>>> James
>>>>
>>>>> *** gcc/ChangeLog ***
>>>>>
>>>>> 2018-xx-xx Sudakshina Das <sudi.das@arm.com>
>>>>> Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
>>>>>
>>>>> * config.gcc (aarch64*-*-*): Add aarch64-bti-insert.o.
>>>>> * gcc/config/aarch64/aarch64.h: Update comment for
>>>>> TRAMPOLINE_SIZE.
>>>>> * config/aarch64/aarch64.c (aarch64_asm_trampoline_template):
>>>>> Update if bti is enabled.
>>>>> * config/aarch64/aarch64-bti-insert.c: New file.
>>>>> * config/aarch64/aarch64-passes.def (INSERT_PASS_BEFORE): Insert
>>>>> bti pass.
>>>>> * config/aarch64/aarch64-protos.h (make_pass_insert_bti):
>>>>> Declare the new bti pass.
>>>>> * config/aarch64/aarch64.md (unspecv): Add UNSPECV_BTI_NOARG,
>>>>> UNSPECV_BTI_C, UNSPECV_BTI_J and UNSPECV_BTI_JC.
>>>>> (bti_noarg, bti_j, bti_c, bti_jc): New define_insns.
>>>>> * config/aarch64/t-aarch64: Add rule for aarch64-bti-insert.o.
>>>>>
>>>>> *** gcc/testsuite/ChangeLog ***
>>>>>
>>>>> 2018-xx-xx Sudakshina Das <sudi.das@arm.com>
>>>>>
>>>>> * gcc.target/aarch64/bti-1.c: New test.
>>>>> * gcc.target/aarch64/bti-2.c: New test.
>>>>> * gcc.target/aarch64/bti-3.c: New test.
>>>>> * lib/target-supports.exp
>>>>> (check_effective_target_aarch64_bti_hw): Add new check for
>>>>> BTI hw.
>>>>>
>>>>> Thanks
>>>>> Sudi
>>
next prev parent reply other threads:[~2019-01-10 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 18:38 Sudakshina Das
2018-11-13 14:47 ` Sudakshina Das
2018-11-29 16:50 ` Sudakshina Das
2018-12-14 16:09 ` Sudakshina Das
2018-12-19 15:41 ` James Greenhalgh
2018-12-20 16:44 ` Sudakshina Das
2019-01-09 14:42 ` Sudakshina Das
2019-01-10 15:46 ` Christophe Lyon
2019-01-10 16:55 ` Sudakshina Das [this message]
2022-08-18 0:00 ` Andrew Pinski
2022-08-18 10:10 ` Richard Earnshaw
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=02937f59-56ad-0305-84e2-8406dd1ed47c@arm.com \
--to=sudi.das@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).