public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Xi Ruoyao <xry111@mengyan1223.wang>,
	"Stemmle,Denis" <denis.stemmle@edag.com>,
	gcc-help@gcc.gnu.org
Subject: Re: Tool Qualification GCC
Date: Fri, 11 Mar 2022 17:14:13 +0100	[thread overview]
Message-ID: <e17a2f20-3ded-f797-72b4-e52ae95ef643@embedded-brains.de> (raw)
In-Reply-To: <4718423ebcf24ace31acb7bc96020208f0763f39.camel@mengyan1223.wang>

On 11/03/2022 06:28, Xi Ruoyao via Gcc-help wrote:
> On Thu, 2022-03-10 at 15:27 +0000, Andrew Haley via Gcc-help wrote:
>> On 3/10/22 15:22, Stemmle, Denis wrote:
>>> - GCC, V 7.5
>>>
>>> For the tools mentioned, could you please answer the following list
>>> of questions and provide us with the relevant documentation?
>> You really should be asking these questions of the supplier from which
>> you downloaded GCC. You are talking to a list which helps people use
>> GCC.
> Quote from the COPYING file in GCC source tree (transformed to sentence
> case):
> 
>                  NO WARRANTY
> 
>    11. Because the program is licensed free of charge, there is no
> warranty
> for the program, to the extent permitted by applicable law.  Except when
> otherwise stated in writing the copyright holders and/or other parties
> provide the program "as is" without warranty of any kind, either
> expressed
> or implied, including, but not limited to, the implied warranties of
> merchantability and fitness for a particular purpose.  The entire risk
> as
> to the quality and performance of the program is with you.  Should the
> program prove defective, you assume the cost of all necessary servicing,
> repair or correction.
> 
>    12. In no event unless required by applicable law or agreed to in
> writing
> will any copyright holder, or any other party who may modify and/or
> redistribute the program as permitted above, be liable to you for
> damages,
> including any general, special, incidental or consequential damages
> arising
> out of the use or inability to use the program (including but not
> limited
> to loss of data or data being rendered inaccurate or losses sustained by
> you or third parties or a failure of the program to operate with any
> other
> programs), even if such holder or other party has been advised of the
> possibility of such damages.

No warranty from the open source community doesn't mean that GCC cannot 
be used in critical environments. This is just the wrong mailing list to 
ask such a list of questions.

-- 
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

      reply	other threads:[~2022-03-11 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 15:22 Stemmle, Denis
2022-03-10 15:27 ` Andrew Haley
2022-03-11  5:28   ` Xi Ruoyao
2022-03-11 16:14     ` Sebastian Huber [this message]

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=e17a2f20-3ded-f797-72b4-e52ae95ef643@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=denis.stemmle@edag.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=xry111@mengyan1223.wang \
    /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).