Hi Maheedhar,
TF-A’s Coverity analysis does not check against the MISRA rules; rather, we use another static analysis tool to do MISRA analysis. Specifically, our Coverity analysis is limited to what is provided for open-source projects via Coverity Scan.
Would you be able to share the MISRA violations you are seeing?
Regards, Chris
From: Manish Pandey2 via TF-A tf-a@lists.trustedfirmware.org Date: Friday, 7 March 2025 at 13:15 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org, Bollapalli, Maheedhar Sai MaheedharSai.Bollapalli@amd.com Cc: Belsare, Akshay akshay.belsare@amd.com, Nagal, Amit amit.nagal@amd.com, Simek, Michal michal.simek@amd.com Subject: [TF-A] Re: Coverity scan infra HI Maheedhar,
Regarding transfer-list library, i can confirm that we are in process of hosting it as a standalone library on trustedfirmware.org which can be imported by other projects (including TF-A). So, you can ignore these failures for now.
Regarding Could you please share Coverity configuration used in TF-A upstream CI pipeline ? I am not an expert on CI pipeline, i will let others respond.
thanks Manish
________________________________ From: Bollapalli, Maheedhar Sai via TF-A tf-a@lists.trustedfirmware.org Sent: 28 February 2025 11:33 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org Cc: Belsare, Akshay akshay.belsare@amd.com; Nagal, Amit amit.nagal@amd.com; Simek, Michal michal.simek@amd.com Subject: [TF-A] Coverity scan infra
[AMD Official Use Only - AMD Internal Distribution Only]
Hi TF-A Team,
With our internal Coverity infrastructure we are seeing multiple MISRA C issues reported (enforced) for transfer-list, while TF-A upstream CI pipeline reports only subset of those violation issues. Could you please share Coverity configuration used in TF-A upstream CI pipeline ?
Regards, Maheedhar. -- TF-A mailing list -- tf-a@lists.trustedfirmware.org To unsubscribe send an email to tf-a-leave@lists.trustedfirmware.org