GCC 11 and Static Analysis
joel at rtems.org
Fri Jan 29 13:15:13 UTC 2021
On Fri, Jan 29, 2021, 6:49 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:
> Hello Matthew,
> On 29/01/2021 10:14, Matthew J Fletcher wrote:
> > Hi,
> > Does RTEMS trunk roughly follow GCC releases ?,. i've seen discussion
> > of GCC 11 on the dev mailing list.
> you can already try out the GCC 11 based tools with the experimental
> RTEMS 7 tool chain available in the RSB.
> > I wonder if we (RTEMS users) could take advantage of the new static
> > analysis options in GCC 11.
> > <
> > Would seem very useful for embedded projects where runtime analysis is
> > difficult.
> Yes, you can give it a try. I never used it myself. The Coverity scan
> alone keeps me busy.
Agreed. I had privately chatted with Gedare about this. He and some
students had planned to or have looked at llvm's analyzer but this should
be an easy step.
The question on all these types analysis tools is how to manage the output.
As a project, we do Coverity runs on leon3 for consistency. BSP doesn't
matter for you if you want to pick at issues. But if it has warnings now,
this will only increase the number.
And it would be nice to think in terms of having automated reports
available for the community and a scoreboard of some sort to track progress.
But honestly, I've been reporting on warnings and analysis issues for
years. Sometimes filing tickets. Sometimes fixing. It is an endless quest
and hard to get broad help.
In fairness, issues in common code gets fixed. Issues in random device
drivers can tend to linger.
Please experiment and report.
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> email: sebastian.huber at embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax: +49-89-18 94 741 - 08
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> users mailing list
> users at rtems.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users