11---
22title : Arm®v8-M Security Extensions <br /> Requirements on Development Tools
3- version : 1.2
4- date-of-issue : 06 April 2022
3+ version : 1.3
4+ date-of-issue : 04 August 2023
55set-quote-highlight : true
66# LaTeX specific variables
77copyright-text : Copyright 2019, 2021-2023 Arm Limited and/or its affiliates <open-source-office@arm.com>.
8- draftversion : true
8+ draftversion : false
99# Jekyll specific variables
1010header_counter : true
1111toc : true
@@ -121,23 +121,14 @@ Copyright 2019, 2021-2023 Arm Limited and/or its affiliates <open-source-office@
121121
122122## Change control
123123
124- ### Current status and anticipated changes
125-
126- This document is a development version based on release 1.1.
127-
128- Anticipated changes to this document include:
129-
130- * Typographical corrections.
131- * Clarifications.
132- * Compatible extensions.
133-
134124### Change history
135125
136- | Issue | Date | By | Change |
137- | :--- | :--- | :--- | :--- |
138- | 1.0 | 23/10/2015 | Arm | First release |
139- | 1.1 | 01/11/2019 | Arm | Second release |
140- | 1.2 | 06 April 2022 | Arm | See [ Changes for version 1.2] ( #changes-for-version-1.2 ) |
126+ | Issue | Date | By | Change |
127+ | :--- | :--- | :--- | :--- |
128+ | 1.0 | 23/10/2015 | Arm | First release |
129+ | 1.1 | 01/11/2019 | Arm | Second release |
130+ | 1.2 | 06 April 2022 | Arm | See [ Changes for version 1.2] ( #changes-for-version-1.2 ) |
131+ | 1.3 | 04 August 2023 | Arm | See [ Changes for version 1.3] ( #changes-for-version-1.3 ) |
141132
142133#### Changes for version 1.2
143134
@@ -154,14 +145,15 @@ Anticipated changes to this document include:
154145 NS nsfunc(struct s);` to ` struct s NS (* nsfunc)(struct
155146 s);`. Non-secure functions have to be function pointers.
156147
157- #### Changes for next release
148+ #### Changes for version 1.3
158149
159150* Removed incorrect optimisation remark in section
160151 [ Arguments on the stack and floating point handling] ( #arguments-on-the-stack-and-floating-point-handling ) .
161152* Removed incorrect information about the floating-point ABI used in
162153 [ Arguments on the stack and floating point handling] ( #arguments-on-the-stack-and-floating-point-handling ) .
163154* Corrected description and example in section
164155 [ Non-secure function pointers] ( #non-secure-function-pointer ) .
156+ * Fixed typos.
165157
166158## References
167159
@@ -1376,14 +1368,14 @@ The global variable `fp` is of a non-secure function type but can hold the
13761368address of a secure or non-secure function. Arm recommends that you do not
13771369share this variable.
13781370
1379- Since ` fp ` can hold either type of function, the compiler may generate code
1371+ Since ` fp ` can hold either type of function, the compiler might generate code
13801372to save and clear registers in preparation for a security state transition even
13811373if the function call nevers performs such transition at run-time.
13821374
13831375To mitigate this, an nsfptr provides a way to test at run-time the
13841376security state that will be targeted when performing a call through
13851377this pointer. By using the nsfptr related intrinsics, it is
1386- possible to check at run-time which function call to perform and thus
1378+ possible to check at run-time which function call to perform and therefore
13871379avoid unnecessary register context saving and clearing.
13881380
13891381``` c
0 commit comments