public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "quentin at armitage dot org.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101451] Incorrect -Wstringop-truncation warning
Date: Thu, 12 Aug 2021 14:06:54 +0000	[thread overview]
Message-ID: <bug-101451-4-sUD2H2KEJi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101451-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101451

--- Comment #2 from Quentin Armitage <quentin at armitage dot org.uk> ---
Created attachment 51297
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51297&action=edit
ipvswrapper.i for strncpy truncated warning

The following warning is generated:

gcc -c -o ipvswrapper.o1 -O2 -Wstringop-truncation ipvswrapper.i
In file included from /usr/include/string.h:519,
                 from ../../lib/timer.h:28,
                 from ../../keepalived/include/vrrp.h:40,
                 from ../../keepalived/include/ipvswrapper.h:29,
                 from ipvswrapper.c:34:
In function ‘strncpy’,
    inlined from ‘ipvs_set_srule’ at ipvswrapper.c:494:7:
/usr/include/bits/string_fortified.h:95:10: warning: ‘__builtin_strncpy’ output
may be truncated copying 15 bytes from a string of length 15
[-Wstringop-truncation]
   95 |   return __builtin___strncpy_chk (__dest, __src, __len,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   96 |                                   __glibc_objsize (__dest));
      |                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~

  parent reply	other threads:[~2021-08-12 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 13:26 [Bug c/101451] New: " quentin at armitage dot org.uk
2021-08-11  2:18 ` [Bug tree-optimization/101451] " pinskia at gcc dot gnu.org
2021-08-12 14:06 ` quentin at armitage dot org.uk [this message]
2021-08-12 14:08 ` quentin at armitage dot org.uk
2021-08-12 20:53 ` msebor at gcc dot gnu.org
2021-08-12 21:05 ` quentin at armitage dot org.uk
2021-08-12 21:09 ` quentin at armitage dot org.uk

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=bug-101451-4-sUD2H2KEJi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).