1
- Functions marked as ` C- cmse-nonsecure-call` place restrictions on their
1
+ Functions marked as ` cmse-nonsecure-call ` place restrictions on their
2
2
inputs and outputs.
3
3
4
4
- inputs must fit in the 4 available 32-bit argument registers. Alignment
@@ -12,12 +12,12 @@ see [arm's aapcs32](https://github.com/ARM-software/abi-aa/releases).
12
12
13
13
Erroneous code example:
14
14
15
- ``` ignore (only fails on supported targets )
16
- #![feature(abi_c_cmse_nonsecure_call )]
15
+ ``` ignore (host errors will not match for target )
16
+ #![feature(abi_cmse_nonsecure_call )]
17
17
18
18
#[no_mangle]
19
19
pub fn test(
20
- f: extern "C- cmse-nonsecure-call" fn(u32, u32, u32, u32, u32) -> u32,
20
+ f: extern "cmse-nonsecure-call" fn(u32, u32, u32, u32, u32) -> u32,
21
21
) -> u32 {
22
22
f(1, 2, 3, 4, 5)
23
23
}
@@ -27,12 +27,12 @@ Arguments' alignment is respected. In the example below, padding is inserted
27
27
so that the ` u64 ` argument is passed in registers r2 and r3. There is then no
28
28
room left for the final ` f32 ` argument
29
29
30
- ``` ignore (only fails on supported targets )
31
- #![feature(abi_c_cmse_nonsecure_call )]
30
+ ``` ignore (host errors will not match for target )
31
+ #![feature(abi_cmse_nonsecure_call )]
32
32
33
33
#[no_mangle]
34
34
pub fn test(
35
- f: extern "C- cmse-nonsecure-call" fn(u32, u64, f32) -> u32,
35
+ f: extern "cmse-nonsecure-call" fn(u32, u64, f32) -> u32,
36
36
) -> u32 {
37
37
f(1, 2, 3.0)
38
38
}
0 commit comments