Jonatan Antoni

Hi @AbhijitInamdar5, Actually, the Linker symbols `bss_start` and `bss_end` *are* defined in the latest Linker script, e.g. https://github.com/ARM-software/CMSIS_5/blob/cbfe6e37b2d1282f754edc6af4d22bb1073dc4b2/Device/ARM/ARMCM3/Source/GCC/gcc_arm.ld#L244-L253 The loop you are referring to is the copy table not the...

Hi @Sherryzhang2, Can you provide us a minimal reproducer example for this issue? May I ask you to check if the issue still exists in latest release 5.8.0, please? Thanks,...

Hi @myronvsqm, My I ask you to check if the following alternative implementation would work for you, please? ```C __STATIC_FORCEINLINE void __TZ_set_STACKSEAL_S (uint32_t* stackTop) { stackTop[0] = (uint32_t)(__TZ_STACK_SEAL_VALUE); stackTop[1] =...

Hi all, I agree this is unusual. The reason for this solution was to hide the symbols from global scope. The implementation has been reviewed by Compiler experts confirming this...

Hi @flit, Sure, we discussed last time if we should add these pragmas. I think this can be done. Reworking the code would need to be done very carefully not...

@ilg-ul, please provide a PR fixing this issue for your case. I.e. by adding the required pragma like `#pragma GCC diagnostic ignored "-Wnested-externs"`. Thanks.

> My current workaround was to define __PROGRAM_START and so the entire code is skipped, and the warning is no longer triggered. But this a kludge. If you guys think...

Hi @utsavm9, RTX4 is not maintained anymore. I suggest to use RTX5 instead. Cheers, Jonatan

Hi @versaloon, This seems to be a duplicate of #617. Unfortunately, we don't have a satisfying solution, yet. Cheers, Jonatan

System headers are typically not included directly but used through device header. I guess that's why this laziness never became a real issue.