From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
<gcc-patches@gcc.gnu.org>
Cc: <Richard.Ball@arm.com>, <yvan.roux@foss.st.com>
Subject: Re: [PATCH v2] testsuite: Verify r0-r3 are extended with CMSE
Date: Wed, 22 May 2024 21:49:45 +0200 [thread overview]
Message-ID: <a9f3fc5c-ea6f-41af-a806-e71c1aadaa9c@foss.st.com> (raw)
In-Reply-To: <4a67aa30-18ab-4ca3-9536-bab7b70b3367@arm.com>
Hi,
I've now pushed the below change to the following branches with the
corresponding commit id.
trunk: 9ddad76e98ac8f257f90b3814ed3c6ba78d0f3c7
releases/gcc-14: da3a6b0dda45bc676bb985d7940853b50803e11a
releases/gcc-13: 75d394c20b0ad85dfe8511324d61d13e453c9285
releases/gcc-12: d9c89402b54be4c15bb3c7bcce3465f534746204
releases/gcc-11: 08ca81e4b49bda153d678a372df7f7143a94f4ad
Kind regards,
Torbjörn
On 2024-05-22 13:54, Richard Earnshaw (lists) wrote:
> On 22/05/2024 12:14, Torbjorn SVENSSON wrote:
>> Hello Richard,
>>
>> Thanks for the reply.
>>
>> From my point of view, at least the -fshort-enums part should be on all branches. Just to be clean, maybe it's easier to backport the entire patch?
>
> Yes, that's a fair point. I was only thinking about the broadening of the test to the other argument registers when I said that.
>
> So, just to be clear, OK all.
>
> R.
>
>>
>> Unless you have an objection, I would like to go ahead and just backport it to all branches.
>>
>> Kind regards,
>> Torbjörn
>>
>> On 2024-05-22 12:55, Richard Earnshaw (lists) wrote:
>>> On 06/05/2024 12:50, Torbjorn SVENSSON wrote:
>>>> Hi,
>>>>
>>>> Forgot to mention when I sent the patch that I would like to commit it to the following branches:
>>>>
>>>> - releases/gcc-11
>>>> - releases/gcc-12
>>>> - releases/gcc-13
>>>> - releases/gcc-14
>>>> - trunk
>>>>
>>>
>>> Well you can [commit it to the release branches], but I'm not sure it's essential. It seems pretty unlikely to me that this would regress on a release branch without having first regressed on trunk.
>>>
>>> R.
>>>
>>>> Kind regards,
>>>> Torbjörn
>>>>
>>>> On 2024-05-02 12:50, Torbjörn SVENSSON wrote:
>>>>> Add regression test to the existing zero/sign extend tests for CMSE to
>>>>> verify that r0, r1, r2 and r3 are properly extended, not just r0.
>>>>>
>>>>> boolCharShortEnumSecureFunc test is done using -O0 to ensure the
>>>>> instructions are in a predictable order.
>>>>>
>>>>> gcc/testsuite/ChangeLog:
>>>>>
>>>>> * gcc.target/arm/cmse/extend-param.c: Add regression test. Add
>>>>> -fshort-enums.
>>>>> * gcc.target/arm/cmse/extend-return.c: Add -fshort-enums option.
>>>>>
>>>>> Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
>>>>> ---
>>>>> .../gcc.target/arm/cmse/extend-param.c | 21 +++++++++++++++----
>>>>> .../gcc.target/arm/cmse/extend-return.c | 4 ++--
>>>>> 2 files changed, 19 insertions(+), 6 deletions(-)
>>>>>
>>>>> diff --git a/gcc/testsuite/gcc.target/arm/cmse/extend-param.c b/gcc/testsuite/gcc.target/arm/cmse/extend-param.c
>>>>> index 01fac786238..d01ef87e0be 100644
>>>>> --- a/gcc/testsuite/gcc.target/arm/cmse/extend-param.c
>>>>> +++ b/gcc/testsuite/gcc.target/arm/cmse/extend-param.c
>>>>> @@ -1,5 +1,5 @@
>>>>> /* { dg-do compile } */
>>>>> -/* { dg-options "-mcmse" } */
>>>>> +/* { dg-options "-mcmse -fshort-enums" } */
>>>>> /* { dg-final { check-function-bodies "**" "" "" } } */
>>>>> #include <arm_cmse.h>
>>>>> @@ -78,7 +78,6 @@ __attribute__((cmse_nonsecure_entry)) char enumSecureFunc (enum offset index) {
>>>>> if (index >= ARRAY_SIZE)
>>>>> return 0;
>>>>> return array[index];
>>>>> -
>>>>> }
>>>>> /*
>>>>> @@ -88,9 +87,23 @@ __attribute__((cmse_nonsecure_entry)) char enumSecureFunc (enum offset index) {
>>>>> ** ...
>>>>> */
>>>>> __attribute__((cmse_nonsecure_entry)) char boolSecureFunc (bool index) {
>>>>> -
>>>>> if (index >= ARRAY_SIZE)
>>>>> return 0;
>>>>> return array[index];
>>>>> +}
>>>>> -}
>>>>> \ No newline at end of file
>>>>> +/*
>>>>> +**__acle_se_boolCharShortEnumSecureFunc:
>>>>> +** ...
>>>>> +** uxtb r0, r0
>>>>> +** uxtb r1, r1
>>>>> +** uxth r2, r2
>>>>> +** uxtb r3, r3
>>>>> +** ...
>>>>> +*/
>>>>> +__attribute__((cmse_nonsecure_entry,optimize(0))) char boolCharShortEnumSecureFunc (bool a, unsigned char b, unsigned short c, enum offset d) {
>>>>> + size_t index = a + b + c + d;
>>>>> + if (index >= ARRAY_SIZE)
>>>>> + return 0;
>>>>> + return array[index];
>>>>> +}
>>>>> diff --git a/gcc/testsuite/gcc.target/arm/cmse/extend-return.c b/gcc/testsuite/gcc.target/arm/cmse/extend-return.c
>>>>> index cf731ed33df..081de0d699f 100644
>>>>> --- a/gcc/testsuite/gcc.target/arm/cmse/extend-return.c
>>>>> +++ b/gcc/testsuite/gcc.target/arm/cmse/extend-return.c
>>>>> @@ -1,5 +1,5 @@
>>>>> /* { dg-do compile } */
>>>>> -/* { dg-options "-mcmse" } */
>>>>> +/* { dg-options "-mcmse -fshort-enums" } */
>>>>> /* { dg-final { check-function-bodies "**" "" "" } } */
>>>>> #include <arm_cmse.h>
>>>>> @@ -89,4 +89,4 @@ unsigned char __attribute__((noipa)) enumNonsecure0 (ns_enum_foo_t * ns_foo_p)
>>>>> unsigned char boolNonsecure0 (ns_bool_foo_t * ns_foo_p)
>>>>> {
>>>>> return ns_foo_p ();
>>>>> -}
>>>>> \ No newline at end of file
>>>>> +}
>>>
>
prev parent reply other threads:[~2024-05-22 19:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 15:55 [PATCH] arm: Zero/Sign extends for CMSE security Richard Ball
2024-04-25 10:01 ` Richard Earnshaw (lists)
2024-04-25 11:47 ` Torbjorn SVENSSON
2024-04-25 14:25 ` Richard Ball
2024-04-26 8:39 ` Torbjorn SVENSSON
2024-04-26 9:19 ` Richard Earnshaw (lists)
2024-04-27 14:13 ` [PATCH] testsuite: Verify r0-r3 are extended with CMSE Torbjörn SVENSSON
2024-04-30 15:11 ` Richard Earnshaw (lists)
2024-04-30 15:37 ` Torbjorn SVENSSON
2024-04-30 16:50 ` Richard Earnshaw (lists)
2024-05-02 10:50 ` [PATCH v2] " Torbjörn SVENSSON
2024-05-06 11:50 ` Torbjorn SVENSSON
2024-05-14 11:01 ` [PING] " Torbjorn SVENSSON
2024-05-21 11:06 ` [PING^2] " Torbjorn SVENSSON
2024-05-22 10:55 ` Richard Earnshaw (lists)
2024-05-22 11:14 ` Torbjorn SVENSSON
2024-05-22 11:54 ` Richard Earnshaw (lists)
2024-05-22 19:49 ` Torbjorn SVENSSON [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=a9f3fc5c-ea6f-41af-a806-e71c1aadaa9c@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=Richard.Ball@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=yvan.roux@foss.st.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).