Page MenuHomePhabricator

TF-A: Piping source code to $CC complicates usage of static analysis tools
Open, Needs TriagePublic

Description

I'm working on implementing MISRA testing for TF-A, using the ECLAIR tool: https://linaro.atlassian.net/browse/TFC-10 .

One of the complications I'm seeing is with this code: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/make_helpers/build_macros.mk#n502 , which pipes source code directly to $CC. When captured by the ECLAIR static analysis tool, this source code assigned a name like _ROOT/dev/pipe/df399ae0, where last component is randomized and differs from build to build, and then leads to spurious differences in reports between builds, which in turns complicates reveiw and analysis of these reports by developers.

Currently, I have no other choice as to look for a ways to disabled/filter out reporting for the piping code altogether, which of course will lead to less precises MISRA analysis. Instead, it would be better if dynamically generated source code was stored in a file, and this file was explicitly passed to the compiler.

Event Timeline

pfalcon created this task.Aug 9 2022, 3:00 PM