|
Questions on MISRA Rules
|
|
8
|
581
|
August 27, 2024
|
|
Should I set anything in SonarQube to analyze against MISRA C++ 2023?
|
|
3
|
179
|
April 29, 2024
|
|
[Webinar] Discover what’s new in MISRA C++ 2023 with Andreas Weis
|
|
1
|
886
|
December 15, 2023
|
|
MISRA-C Rule 21.8
|
|
2
|
569
|
October 20, 2023
|
|
Misra C:2012 (including AMD4) compliance and plans for 2023?
|
|
1
|
1146
|
June 9, 2023
|
|
C++ analysis engine covers more rules from MISRA C++ 2008 standard
|
|
2
|
1497
|
February 9, 2023
|
|
Need float exclusion for rule cpp:S813
|
|
4
|
667
|
December 15, 2022
|
|
Does SonarQube supports MISRA Standard?
|
|
14
|
9429
|
June 2, 2022
|
|
Checkers in SonarQube
|
|
7
|
3806
|
May 4, 2021
|
|
C rules addon with the Developer Edition
|
|
2
|
1132
|
July 15, 2020
|
|
C-STAT and MISRA importing results
|
|
3
|
729
|
June 19, 2020
|
|
How to include misra in sonarqube? (willing to purchase if needed)
|
|
8
|
5691
|
May 29, 2020
|
|
Why does SonarQube raise a MISRA-C critical remark <<Function names should be used either as a call […]>> on the “startup” code for ARM Cortex-M3?
|
|
4
|
1066
|
March 19, 2020
|
|
New Rules for MISRA2012: Rules 5.1 and 5.2, 5.4 and 5.5
|
|
1
|
6207
|
February 7, 2020
|
|
Mandatory rule MISRA-C:2012 19.1 not supported
|
|
1
|
1662
|
February 7, 2020
|
|
MISRA-C:2012 Mandatory rule 13.6 not supported
|
|
3
|
1755
|
February 6, 2020
|
|
Wrong naming of rule: "switch" statements should have at least 3 "case" clauses
|
|
2
|
1531
|
July 14, 2020
|
|
SonarQube MISRA compliance sheet
|
|
4
|
2249
|
February 3, 2020
|
|
MISRA-C 2004 rule 5.5
|
|
2
|
840
|
January 6, 2020
|
|
Sonarqube not reporting misra c violations even though all 4.7k+ rules are activated in the quality profile
|
|
3
|
1210
|
June 19, 2019
|
|
[Blog Post] MISRA C++ 2008 support is on its way
|
|
0
|
753
|
May 29, 2019
|
|
Misra C 2012 support
|
|
1
|
1619
|
February 1, 2019
|
|
MISRA C Compliance
|
|
2
|
2234
|
December 3, 2018
|
|
Misra rule 20.1 check is not accurate
|
|
2
|
1936
|
November 5, 2018
|