1- Functions marked as ` C- cmse-nonsecure-call` place restrictions on their
1+ Functions marked as ` cmse-nonsecure-call ` place restrictions on their
22inputs and outputs.
33
44- 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).
1212
1313Erroneous code example:
1414
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 )]
1717
1818#[no_mangle]
1919pub 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,
2121) -> u32 {
2222 f(1, 2, 3, 4, 5)
2323}
@@ -27,12 +27,12 @@ Arguments' alignment is respected. In the example below, padding is inserted
2727so that the ` u64 ` argument is passed in registers r2 and r3. There is then no
2828room left for the final ` f32 ` argument
2929
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 )]
3232
3333#[no_mangle]
3434pub 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,
3636) -> u32 {
3737 f(1, 2, 3.0)
3838}
0 commit comments