public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93517] bogus -Wrestrict on sprintf with unknown strings bounded by array size
Date: Tue, 28 Apr 2020 14:23:38 +0000	[thread overview]
Message-ID: <bug-93517-4-sLBS8T7jaK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93517-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
This bug is different than PR94815 because here the warning code should be able
to determine that the sprintf call cannot overlap based on the sizes of the
array arguments that put an upper bound on the lengths of the strings stored in
the arrays.  (In PR94815 the sizes of the arrays aren't known and neither are
the lengths of the strings stored in them.)

  parent reply	other threads:[~2020-04-28 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93517-4@http.gcc.gnu.org/bugzilla/>
2020-04-28 11:56 ` vincent.riviere at freesbee dot fr
2020-04-28 14:23 ` msebor at gcc dot gnu.org [this message]
2022-05-25 16:31 ` msebor at gcc dot gnu.org

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-93517-4-sLBS8T7jaK@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).