[sw] Build software with different compiler flag combinations (e.g. inlining disabled) in CI
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
It would be useful to have the software build be more resilient to compiler flag changes. To acheive this we could pick some combinations to test in CI.
#9216 would not have been needed if there was a build done in CI with `-O0` or `-fno-inline` enabled. At a minimum it may make sense to have a 'no optimizations' build. We could also consider doing builds with sanitizers enabled and/or different optimization levels (e.g. `-O3`,`-Os` and `-Oz`).
Contributor guide
Research direction
Start by reviewing issue #9216 and the repository's current CI build configuration. Define which compiler-flag combinations are in scope, then verify that the selected builds run successfully in CI and expose relevant failures.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100