RTEMS | build: Check the GCC build key (!1146)

[Sebastian Huber (@sebhub)]

Sebastian Huber created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1146

Project:Branches: sebhub/rtems:tool-build-key-support-without-ai-code to rtems/rtos/rtems:main
Author:   Sebastian Huber

Reviewer: Chris Johns

## Summary

build: Check the GCC build key

Query the GCC build key and check it against the required value.

There are dependencies between the RTEMS sources and external interfaces
provided by Newlib and GCC.  For example, POSIX API interfaces may
change due to POSIX standard updates.  The GCC build key is used to
provide an indication that the present tools meet the requirements of
the RTEMS sources.

Add the GCC_BUILD_KEY_POLICY build option to define the checking policy.
The GCC build key policy defines how the build key of the present
compiler is checked against the required build key.  While the policy is
"ERROR", if the GCC build key has not the expected value, then the build
configuration process produces a fatal error.  While the policy is
"WARNING", if the GCC build key has not the expected value, then the
build configuration process produces a warning message.  While the
policy is "IGNORE", the GCC build key is not checked at all.  The
default policy is "WARNING".

Close #5521.

No help of AI was used in this change.

Signed-off-by: Sebastian Huber <sebastian.huber at embedded-brains.de>

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1146
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260318/bcd38980/attachment.htm>