Hi,
this is an old TI Project, which uses C2000 compiler 6.x.x which had multiple issues already - e.g. it did not show size defines which made sonarscanner fail silently with zero issues ^^ see here: Sonarlint seems to work fine but finds zero issues in all analyzed code
The compiler is really the issue here, and we are aware of that. still, for “reasons” we cannot update the compiler now. we mitigated the other issue by automatically adding the size defines to the compile_commands.json after generating it, so the code checking itself works fine now. but as [[fallthrough]] is available since c++17 and c23 as far as i googled very quickly, this compiler has no idea how to deal with that.
there should be many compilers out there which don’t allow that. i hope that there will be alternative ways to allow fallthrough, marking them as false positive will let them go unnoticed when we finally update the compiler. we disabled the rule for now.
is there a global intentional-thing? For example, in Axivion, any rule can be temporary disabled for one line by writing a comment in the form of
//AXIVION: RULE123.456 I did this because of these reasons
which is simple, valid for any c compiler back to the olden days. the text of the reasoning is then automatically added to the issue in the overview.