3 Commits

Author	SHA1	Message	Date
linD026	d6e1044aa7	CI: introduce GCC static analysis ... Since GCC version 10, there has been a new option -fanalyzer for static analysis. It can make the CI pipeline more comprehensive. Also, the static analysis updates in GCC 11, but we cannot install the GCC 11 in ubuntu 20.04 straightforwardly right now, which is the GitHub workflow environment (see status-check.yaml). For this reason, we stay at the GCC 10. Close #117 Reference - https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Static-Analyzer-Options.html - https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10 - https://lwn.net/Articles/870290/ - https://developers.redhat.com/blog/2021/01/28/static-analysis-updates-in-gcc-11 - 7d73c3e9c5	2021-10-08 19:41:22 +08:00
linD026	25d82ec47f	CI: Integrate the Sparse into the CI pipeline ... Sparse[1] is a semantic parser for C language, it can find out the potential problem of the example code. [1] https://www.kernel.org/doc/html/latest/dev-tools/sparse.html	2021-09-15 12:43:56 +08:00
linD026	5070fcd9d0	CI: Run static analysis with Cppcheck (#105) ... Cppcheck[1] is integrated into CI pipeline for running static analysis. However, Cppcheck is known to report false-positive, and we have to suppress some warnings in advance. [1] https://cppcheck.sourceforge.io/	2021-09-14 00:52:04 +08:00