-
Notifications
You must be signed in to change notification settings - Fork 15.4k
[docs] Add documentation for LLVM Qualification Group #145331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| ======================== | ||
| LLVM Qualification Group | ||
| ======================== | ||
|
|
||
| Introduction | ||
| ============ | ||
|
|
||
| The LLVM Qualification Group is an open working group within the LLVM community. | ||
| It was created to coordinate efforts around enabling the use of LLVM components | ||
| in safety-critical applications such as those governed by ISO 26262 (automotive), | ||
| DO-178C (aerospace), and EN 50128 (railways). | ||
|
|
||
| Motivation | ||
| ========== | ||
|
|
||
| LLVM is increasingly used in safety-critical domains (e.g., automotive, aerospace, medical), | ||
| but currently lacks a shared structure to address the specific needs of functional safety, | ||
| such as systematic assurance arguments, tool qualification artifacts, and their associated | ||
| documentation. | ||
|
|
||
| An more open, upstream, reusable, and collaborative approach would benefit the wider ecosystem. | ||
| This group serves as a public forum for those interested in improving LLVM’s suitability for | ||
| use in such environments. | ||
|
|
||
| Goals | ||
| ===== | ||
|
|
||
| The Qualification Group aims to: | ||
|
|
||
| * Facilitate open discussion around tool confidence and qualification practices | ||
| * Identify areas for upstream improvements (e.g., traceability hooks, quality evidence) | ||
| * Share safety-relevant documentation and argumentation templates | ||
| * Coordinate efforts across users and vendors working toward similar goals | ||
| * Act as a point of contact for safety-related collaboration | ||
|
|
||
| The group is non-enforcing and does not control any part of the codebase. | ||
| All technical decisions remain subject to the standard LLVM review and governance process. | ||
|
|
||
| Participation | ||
| ============= | ||
|
|
||
| Participation is open to anyone interested. The group currently coordinates via: | ||
|
|
||
| * LLVM Discourse (under the "Community" category): https://discourse.llvm.org/ | ||
| * Public working sessions and collaborative documents | ||
| * [Details on working sessions will be shared soon on the GettingInvolved page] | ||
| * Informal discussions on the LLVM Community Discord server (channel to be announced) | ||
|
|
||
| Initial Contributors | ||
| ==================== | ||
|
|
||
| The initial participants include community members and industry contributors with experience | ||
| in compiler development, tool qualification, and functional safety. (To be filled in after PR review.) | ||
|
|
||
| Contact | ||
| ======= | ||
|
|
||
| For more information or to get involved, please refer to the ongoing Discourse thread: | ||
| https://discourse.llvm.org/t/rfc-proposal-to-establish-a-safety-group-in-llvm/86916 | ||
|
|
||
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.