🎉 Update README to declare our support for MISRA C++ 2023 🎉 #1124
Open
MichaelRFairhurst wants to merge 1 commit intomainfrom
Open
🎉 Update README to declare our support for MISRA C++ 2023 🎉 #1124MichaelRFairhurst wants to merge 1 commit intomainfrom
MichaelRFairhurst wants to merge 1 commit intomainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates repository documentation and metadata to reflect completed support for MISRA C++ 2023, including clarifying unsupported rules and updating documented language/compiler requirements.
Changes:
- Mark MISRA C++ 2023
DIR-0-3-2as not supportable and add justification in the supported-rules CSV. - Update the user manual to present MISRA C++ 2023 as implemented, add an explanatory footnote, and revise compiler/flag tables.
- Update the README to list MISRA C++ 2023 as supported and to mention C++17 support, plus adjust the “under development” section.
Show a summary per file
| File | Description |
|---|---|
| rules.csv | Adjusts MISRA C++ 2023 rule supportability metadata for DIR-0-3-2. |
| docs/user_manual.md | Updates coverage/status for MISRA C++ 2023 and revises supported environment tables/footnotes. |
| README.md | Declares MISRA C++ 2023 support and updates language/roadmap statements. |
Copilot's findings
- Files reviewed: 3/3 changed files
- Comments generated: 4
| | 0.25.0 | 2025-01-15 | Mike Fairhurst | Add guidance for the usage of 'strict' queries. | | ||
| | 0.26.0 | 2025-02-12 | Luke Cartey | Describe support for new deviation code identifier formats | | ||
| | 0.27.0 | 2025-05-15 | Luke Cartey | Documented completed support for MISRA C 2023. | | ||
| | 0.27.0 | 2025-05-15 | Mike Fairhurst | Documented completed support for MISRA C++ 2023. | |
| | | [2012 Amendment 4](https://misra.org.uk/app/uploads/2021/06/MISRA-C-2012-AMD4.pdf) | 22 | 22 | 21[^4] | Implemented | | ||
| | | [2023 Third Edition, Second Revision](https://misra.org.uk/product/misra-c2023/) | 221 | 210 | 207[^5] | Implemented | | ||
| | MISRA C++ | [2023](https://misra.org.uk/product/misra-cpp2023/) | 179 | 176[^6] | - | Under development | | ||
| | MISRA C++ | [2023](https://misra.org.uk/product/misra-cpp2023/) | 179 | 175[^6] | - | Implemented | |
Comment on lines
118
to
+122
| For C++ the codebase under analysis must comply with C++14 and use one of the following supported compiler configurations: | ||
|
|
||
| | Compiler | Version | Standard library | Target architecture | Required flags | | ||
| | -------- | ------- | ------------------- | --------------------- | -------------------------------- | | ||
| | clang | 10.0.0 | libstdc++ (default) | x86_64-linux-gnu | -std=c++14 | | ||
| | gcc | 8.4.0 | libstdc++ (default) | x86_64-linux-gnu | -std=c++14 | | ||
| | qcc | 8.3.0 | libc++ (default) | gcc_ntoaarch64le_cxx | -std=c++14 -D_QNX_SOURCE -nopipe | | ||
| | Compiler | Version | Standard library | Target architecture | Language standard flag | Other required flags | | ||
| | -------- | ------- | ------------------- | --------------------- | ---------------------------- | ----------------------- | | ||
| | clang | 10.0.0 | libstdc++ (default) | x86_64-linux-gnu | `-std=c++14` or `-std=c++17` | None | |
| - [MISRA C++ 2023](https://misra.org.uk/product/misra-cpp2023/) - under development - _scheduled for release 2026 Q1/Q2_ | ||
| This product intends to begin development of the following standards in the near future: | ||
|
|
||
| - [MISRA C 2025](https://misra.org.uk/product/misra-cpp2025/) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Still waiting on the last few rules then we can merge this! 🎉
Change request type
.ql,.qll,.qlsor unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.