From: David Brown <david@westcontrol.com>
To: Vishal B Patil <vishal.b.patil@cummins.com>
Cc: Basile Starynkevitch <basile@starynkevitch.net>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC support addition for Safety compliances
Date: Wed, 12 Jul 2023 17:23:06 +0200 [thread overview]
Message-ID: <3c32f69d-a9df-f372-011e-4ff71c9328bc@westcontrol.com> (raw)
In-Reply-To: <CAH6eHdTY8XRWhOkGodrdDeGdUqDEt9aObge8bA2PscE-2KTkhg@mail.gmail.com>
On 12/07/2023 14:43, Jonathan Wakely via Gcc wrote:
> On Wed, 12 Jul 2023 at 10:25, Vishal B Patil via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> Hi Team,
>>
>> Any updates ?
>
> You're not going to get any useful answers.
>
> You asked "Please share the costs and time as well." Costs for what? From whom?
>
> GCC is an open-source project with a diverse community of hundreds of
> contributors. Who are you asking to give you costs? What work are you
> expecting them to do?
>
> It is unlikely that you obtained GCC from https://gcc.gnu.org so you
> should probably talk to whoever provided you with your GCC binaries.
Most people get their GCC binaries for free, and no such source is going
to be able to help for safety compliance or any other kind of
certification. Certification always costs time, effort and money. But
there are suppliers who provide toolchain binaries with commercial
support contract, and which could help with certification. I know Code
Sourcery certainly used to be able to provide language compliance
certification - I have no idea if they still can (it seems they are part
of Siemens these days). Maybe Red Hat (part of IBM) can do so too, and
possibly others. But perhaps that will give the OP a starting point.
David
> For safety compliance you will probably need to talk to a third-party
> who specializes in that. I don't think you will achieve anything by
> asking the GCC project to do that for you.
>
> That's not how open source projects work.
>
>
>
>>
>> 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 prev parent reply other threads:[~2023-07-12 15:23 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
2023-07-12 12:43 ` Jonathan Wakely
2023-07-12 15:23 ` David Brown [this message]
[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=3c32f69d-a9df-f372-011e-4ff71c9328bc@westcontrol.com \
--to=david@westcontrol.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=vishal.b.patil@cummins.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).