RTEMS | Draft: Support for building RTEMS with LLVM toolchains (!1539)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on spec/build/cpukit/optcoverage.yml: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161194

 >    Enable the code and branch coverage support.
 >  enabled-by: true
 >  links: []
 > -name: RTEMS_GCOV_COVERAGE
 > +name: RTEMS_COVERAGE

Please keep the option name `RTEMS_GCOV_COVERAGE`. The build reads only the option names it knows from `config.ini` and ignores every other key. An existing `config.ini` with `RTEMS_GCOV_COVERAGE = True` then builds without coverage, and nothing reports it. Every coverage configuration which exists today breaks in this way.

The clang support does not need a new name. The option can stay as it is, and `enabled-by: clang` selects the compiler flags, the linker flags and the dump implementation. The MR already uses this pattern in `optcoveragecflags-clang.yml` and `objcovllvm.yml`.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161194
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-4n1w3ylcde9zqnlce6wcjg3c0-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


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