From: "Stemmle, Denis" <denis.stemmle@edag.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Cc: "Saydam, Mertkan" <mertkan.saydam@edag.com>,
"Schwarz, Jonas" <jonas.schwarz@edag.com>
Subject: Tool Qualification GCC
Date: Thu, 10 Mar 2022 15:22:14 +0000 [thread overview]
Message-ID: <FR3P281MB106497549CE35710627DCEA4820B9@FR3P281MB1064.DEUP281.PROD.OUTLOOK.COM> (raw)
Hi all,
I work for the EDAG Engineering GmbH as a System Safety Engineer in the Functional Safety department in Weinheim (Germany).
We were asked by Luminar (contact person: Manjeet Bilra) to qualify the software tools used in the development. You were named as our contact regarding the following tool:
- GCC, V 7.5
For the tools mentioned, could you please answer the following list of questions and provide us with the relevant documentation?
Sr. No.
Checkpoints
Response
Remarks
Tools-Classfication&Qualification
1
Is the Tool classified and qualified according to ISO26262?
If yes: what are the resulting outcomes?
- Tool Confidence Level (TCL)
- Maximum ASIL
- Qualification methods
2
If not: Is the tool classified and qualified (or developed) according to a different standard?
3
What are the known malfunctions & whether there is an databank showing previous malfunctions.
4
Is the tool capable of detecting any tool failures?
5
What are the different use cases covered by the tool? Are all listed use cases evaluated as part of the tool Qualification.
6
Do we have the tool test report to confirm the integrity of the tool or confidence in the tool.
8
Is there a tool safety Manual and respective Tool Qualification Report available?
9
Does the tool provide any test suite to qualify the tool at the user end?
10
Are all previous tool defects and resulting patches, generated by the tool manufacturer, documented?
Could it be checked online on the tool manufacturers website?
11
In case there is no tool classification or qualification done at tool supplier side:
a) Are there any additional / alternate measures applied.
b) Is there a rationale to use the tool for safety critical development
Thank you in advance and best regards
Denis Stemmle
Mit freundlichen Grüßen
i.A. Denis Stemmle
Functional Safety Engineer
Abteilung Functional Safety & Cyber Security
Team Funktionale Sicherheit I
EDAG Engineering GmbH
Kompetenzcenter Weinheim
Höhnerweg 2-4 / Bau 101
69469 Weinheim
Mobil: +49 171 4930695
E-Mail: denis.stemmle@edag.com<mailto:denis.stemmle@edag.com>
www.edag.com<http://www.edag.com/>
next reply other threads:[~2022-03-10 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 15:22 Stemmle, Denis [this message]
2022-03-10 15:27 ` Andrew Haley
2022-03-11 5:28 ` Xi Ruoyao
2022-03-11 16:14 ` Sebastian Huber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FR3P281MB106497549CE35710627DCEA4820B9@FR3P281MB1064.DEUP281.PROD.OUTLOOK.COM \
--to=denis.stemmle@edag.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jonas.schwarz@edag.com \
--cc=mertkan.saydam@edag.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).