From: Vishal B Patil <vishal.b.patil@cummins.com>
To: Basile Starynkevitch <basile@starynkevitch.net>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: GCC support addition for Safety compliances
Date: Wed, 12 Jul 2023 09:24:32 +0000 [thread overview]
Message-ID: <SN4PR0501MB379089B8A11796CAAED54B75DC36A@SN4PR0501MB3790.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CY4PR0501MB37799E8520102E8B4DBA47EBDC2FA@CY4PR0501MB3779.namprd05.prod.outlook.com>
Hi Team,
Any updates ?
Regards,
Vishal B Patil
vishal.b.patil@cummins.com
Dahanukar Colony, Kothrud
Pune
Maharashtra
411038
India
-----Original Message-----
From: Vishal B Patil
Sent: Wednesday, July 5, 2023 4:18 PM
To: Basile Starynkevitch <basile@starynkevitch.net>
Subject: RE: GCC support addition for Safety compliances
Hi Team,
Thanks for the response.
Actually required for UL60730, UL6200. Please share the costs and time as well.
Regards,
Vishal B Patil
vishal.b.patil@cummins.com
Dahanukar Colony, Kothrud
Pune
Maharashtra
411038
India
-----Original Message-----
From: Basile Starynkevitch <basile@starynkevitch.net>
Sent: Wednesday, July 5, 2023 4:07 PM
To: Vishal B Patil <vishal.b.patil@cummins.com>
Subject: GCC support addition for Safety compliances
EXTERNAL SENDER: This email originated outside of Cummins. Do not click links or open attachments unless you verify the sender and know the content is safe.
Hello
> Need support from the GCC GNU for the some safety compliances. Can you please guide or check which GCC support the safety compliances.
For safety compliance GCC is probably not enough.
Consider (if allowed by your authorities) using static analysis tools like https://frama-c.com/ or https://www.absint.com/products.htm
Be sure to understand what technically safety compliance means to you.
DOI178C? ISO26262?
Be also aware that safety compliance costs a lot of money and a lot of time. (you'll probably need a budget above 100k€ ou 100kUS$ and about a person*year of developer efforts)
--
Basile Starynkevitch <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
next parent reply other threads:[~2023-07-12 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89859db1-8f61-dec7-491f-23c9ad31ec66@starynkevitch.net>
[not found] ` <CY4PR0501MB37799E8520102E8B4DBA47EBDC2FA@CY4PR0501MB3779.namprd05.prod.outlook.com>
2023-07-12 9:24 ` Vishal B Patil [this message]
2023-07-12 12:43 ` Jonathan Wakely
2023-07-12 15:23 ` David Brown
[not found] ` <CY4PR0501MB37791C2AF5B8884F39B27C71DCA7A@CY4PR0501MB3779.namprd05.prod.outlook.com>
2023-11-01 12:59 ` Jonathan Wakely
2023-07-05 9:23 Vishal B Patil
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=SN4PR0501MB379089B8A11796CAAED54B75DC36A@SN4PR0501MB3790.namprd05.prod.outlook.com \
--to=vishal.b.patil@cummins.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
/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).