[PATCH 0/7, GCC, V8M] ARMv8-M Security Extensions

Kyrill Tkachov kyrylo.tkachov@foss.arm.com
Mon Oct 24 16:14:00 GMT 2016

Hi Andre,

On 24/08/16 12:02, Andre Vieira (lists) wrote:
> On 10/08/16 09:08, Andre Vieira (lists) wrote:
>> On 09/08/16 17:47, Sandra Loosemore wrote:
>>> On 08/09/2016 06:01 AM, Andre Vieira (lists) wrote:
>>>> [snip]
>>>> The documentation is in the ARMV8-M Security Extensions in: ARM®v8-M
>>>> Security Extensions: Requirements on Development Tools document I linked
>>>> in the email above and subsequent emails
>>>> (http://infocenter.arm.com/help/topic/com.arm.doc.ecm0359818/index.html).
>>>> Also per patch I refer to the relevant sections. So for instance in
>>>> PATCH 3/7 refers to Section 5.4, which describes Entry functions and
>>>> mentions the cmse_nonsecure_entry attribute. Whereas PATCH 7/7 refers to
>>>> Section 5.4.3 of the same document which describes the
>>>> cmse_nonsecure_caller intrinsic which that patch implements.
>>>> Is there a specific intrinsic/attribute you are missing?
>>> You need to at least add entries to the relevant sections in extend.texi
>>> for the new target-specific intrinsic and attributes.  The documentation
>>> there doesn't need to be terribly detailed (one sentence and a link to
>>> the external document is probably all you need), but it's important that
>>> these things be listed in GCC's supported extensions so that users know
>>> they can use them and so that people who see them in code written by
>>> other people can find out what they mean.
>>> -Sandra
>> I see, I did add a new entry to extend.texi for ARMv8-M Security
>> Extensions. I will also mention all intrinsics and attributes there.
>> Thank you.
>> Andre
> I updated the patch series with more documentation in extend.texi and I
> also fixed an issue with the clearing of FPSCR.

Can you please rebase the patches on latest trunk and resend them?
I could not apply the first patch with patch -p1 on today's trunk...
I'll try to get to them this week, sorry for the delay.


> Cheers,
> Andre

More information about the Gcc-patches mailing list