Jonatan Antoni

May I ask you for what reason you enabled that warning? There seems nothing wrong with using this kind of extern declaration. Hence I am now struggling between adding the...

Hi @zejiangfish, I guess this happens because the symbols in question (e.g. `__copy_table_start__`) are linker generated. Hence the compiler doesn't see the definition. We could of course move the type...

Hi @noxuz, Thanks for getting in touch. I had clarified with our Compiler experts back in June last year that these nested declarations should just be fine. Why is this...

@yan12125, which version of GCC are you using? As stated above, the nested declarations should be just fine from C standard point of view. Is this caused by a shortcoming...

Hi @CheMax-Tag, The `extern C` declaration is in all the `core_cmX.h` files. So including the `cmsis_gcc.h` file the regular way (through the device header including the required core header) should...

I agree, if done properly the `extern "C"` should not harm, either. May one of you find the time to raise the required changes as a PR? Would be quite...

Hi @dzid26, I can only speculate because using vanilla Clang is currently not in scope. The "problem" might be the declaration of extern variables with non-external types. Strictly speaking no...

Hi @simtind, thanks for pointing this out. We'll have a look into that one. Cheers, Jonatan

Hi @simtind, sorry, this slipped through while we were working on getting the CMSIS-Pack code to open source. Cheers, Jonatan

Hi @Jegeva, the root cause for this forth and back is basically that SVD isn't designed with a modular approach. Today every device has exactly one single SVD file associated...