From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-200932-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 120354 invoked by alias); 10 Dec 2019 10:52:42 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 119700 invoked by uid 89); 10 Dec 2019 10:52:42 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=UD:htm, luburyanahotmailcom, luburyana@hotmail.com, H*i:Sn1nFTfyXbChb
X-HELO: mail-wm1-f67.google.com
Received: from mail-wm1-f67.google.com (HELO mail-wm1-f67.google.com) (209.85.128.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Dec 2019 10:52:40 +0000
Received: by mail-wm1-f67.google.com with SMTP id p9so2625116wmg.0        for <gcc@gcc.gnu.org>; Tue, 10 Dec 2019 02:52:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=bzaA3t9q4X4Rmdoyju7p2NoxYhCHiO+gpbhk8M95FSg=;        b=ZEH5Ozh2XNCyVEIfTHwpoyQYL0ao7SiRfzyYro/XrB3b7ReenUvp3VVDWfFaUZycRz         IZexucZWTl//nfuorBhAZhOEjG/eqjH/bjhfIKLt5OrRWaKMK1VpihHT+HqkvKOb2zUt         ecaNRFeg+0RpLuDdEmMpF10zTdwcgkS/8RLX0N+qQiHWcCBLr2HFS7u/JwwsqXJ1qTOg         WsPw1MYbf+eWf8h9Wh0CmLZGUrnnZChhnErvDi3PaiCgqat142RQjxTRb/PI3P2xhmed         Qp9pRu7UtFWfVEn4KQ+84gCbpCR7/QZdWeu9XDss+WZaKMM5PGxscZmagPprozXlgWdC         61UA==
MIME-Version: 1.0
References: <4C695126-AB18-4629-A498-76617857DB78@hotmail.com> <CA+=Sn1nFTfyXbChb==FV9xDA_VLoA5EZVtENDa3L_htQ5H1tJA@mail.gmail.com>
In-Reply-To: <CA+=Sn1nFTfyXbChb==FV9xDA_VLoA5EZVtENDa3L_htQ5H1tJA@mail.gmail.com>
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Tue, 10 Dec 2019 10:52:00 -0000
Message-ID: <CAH6eHdR-+okTtcB1aKNMBDsgRdjNMcvHFC+wBOCic68AxXD74A@mail.gmail.com>
Subject: Re: Usage of C11 Annex K Bounds-checking interfaces on GCC
To: li zi <luburyana@hotmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, Andrew Pinski <pinskia@gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-12/txt/msg00150.txt.bz2

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.