You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The warning is fine to warn a user that something is not supported by a compiler but the placement of this warning might be counterproductive - in a header file. It's currently in a header that is being included everywhere as it's part of CMSIS. Therefore when a user compiles their code, it might end up with 100x warnings (all are the same, for each file that depends on CMSIS). It creates lot of noise, that will result in removing this warning after few compilations :-)
Here's the warning: [Pe1105]: #warning directive: No compiler specific solution for __ALIGNED. __ALIGNED is ignored.
I would suggest to have one code file that would warn about this - warning: this feature of cmsis is not supported by this compiler. Or remove that warning and document it what is supported and what not (a user should be aware some extensions are not supported - they are compiler specific. - thus a code using it might not be portable.
The text was updated successfully, but these errors were encountered:
The warning is fine to warn a user that something is not supported by a compiler but the placement of this warning might be counterproductive - in a header file. It's currently in a header that is being included everywhere as it's part of CMSIS. Therefore when a user compiles their code, it might end up with 100x warnings (all are the same, for each file that depends on CMSIS). It creates lot of noise, that will result in removing this warning after few compilations :-)
Here's the warning:
[Pe1105]: #warning directive: No compiler specific solution for __ALIGNED. __ALIGNED is ignored.
I would suggest to have one code file that would warn about this - warning: this feature of cmsis is not supported by this compiler. Or remove that warning and document it what is supported and what not (a user should be aware some extensions are not supported - they are compiler specific. - thus a code using it might not be portable.
The text was updated successfully, but these errors were encountered: