public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: li zi <luburyana@hotmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, Andrew Pinski <pinskia@gmail.com>
Subject: Re: Usage of C11 Annex K Bounds-checking interfaces on GCC
Date: Tue, 10 Dec 2019 10:52:00 -0000	[thread overview]
Message-ID: <CAH6eHdR-+okTtcB1aKNMBDsgRdjNMcvHFC+wBOCic68AxXD74A@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1nFTfyXbChb==FV9xDA_VLoA5EZVtENDa3L_htQ5H1tJA@mail.gmail.com>

On Tue, 10 Dec 2019 at 06:22, Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Mon, Dec 9, 2019 at 10:14 PM li zi <luburyana@hotmail.com> wrote:
> >
> > Hi All,
> > We are using gcc in our projects and we found some of the C standard functions (like memcpy, strcpy) used in gcc may induce security vulnerablities like buffer overflow. Currently we have not found any instances which causes such issues.
>
> Are you using GCC as a compiler or the sources of GCC to do something
> else?  If you are using it as a compiler, GCC does NOT provide the
> libc functions, another project (e.g. glibc) provides those.

And glibc considers them not useful and so doesn't provide them, see
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm

Your question would have been more appropriate on the gcc-help mailing
list, as you're not discussing development of GCC itself.

  reply	other threads:[~2019-12-10 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  6:13 li zi
2019-12-10  6:22 ` Andrew Pinski
2019-12-10 10:52   ` Jonathan Wakely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-10  3:15 li zi
2019-12-14 17:36 ` Martin Sebor
2019-12-15  1:59   ` Jeffrey Walton
2019-12-15 18:25     ` David Brown
2019-12-15 20:02       ` Jeffrey Walton
2019-12-16  2:43         ` Liu Hao
2019-12-16  3:45           ` Jeffrey Walton
2019-12-16  7:52           ` Didier Kryn

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=CAH6eHdR-+okTtcB1aKNMBDsgRdjNMcvHFC+wBOCic68AxXD74A@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=luburyana@hotmail.com \
    --cc=pinskia@gmail.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).