public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113752] [14 Regression] warning: ‘%s’ directive writing up to 10218 bytes into a region of size between 0 and 10240 [-Wformat-overflow=] since r14-261-g0ef3756adf078c
Date: Tue, 13 Feb 2024 11:36:24 +0000	[thread overview]
Message-ID: <bug-113752-4-qRjPLDeO16@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113752-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Anyway, I think the testcase is very similar to
char a[256], *c, *g;

int
foo (void)
{
  if (__builtin_strlen (c) + __builtin_strlen (g) + 5 > 256)
    return 0;
  __builtin_sprintf (a, "abcd%s%s", c, g);
  return 1;
}
which has started diagnosing this with
r12-5014-g6b8b959675a3e14cfdd2145bd62e4260eb193765 at -O2 -Wall -W

  parent reply	other threads:[~2024-02-13 11:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04  4:34 [Bug c/113752] New: [14 Regression] warning: ‘%s’ directive writing up to 10218 bytes into a region of size between 0 and 10240 [-Wformat-overflow=] hjl.tools at gmail dot com
2024-02-04  4:47 ` [Bug tree-optimization/113752] " pinskia at gcc dot gnu.org
2024-02-04  5:58 ` hjl.tools at gmail dot com
2024-02-04  6:15 ` hjl.tools at gmail dot com
2024-02-12  9:46 ` [Bug tree-optimization/113752] [14 Regression] warning: ‘%s’ directive writing up to 10218 bytes into a region of size between 0 and 10240 [-Wformat-overflow=] since r14-261-g0ef3756adf078c aldyh at gcc dot gnu.org
2024-02-12 10:09 ` jakub at gcc dot gnu.org
2024-02-12 10:23 ` jakub at gcc dot gnu.org
2024-02-12 13:52 ` hjl.tools at gmail dot com
2024-02-13 11:36 ` jakub at gcc dot gnu.org [this message]
2024-03-07 20:41 ` law at gcc dot gnu.org
2024-05-07  7:44 ` [Bug tree-optimization/113752] [14/15 " rguenth 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-113752-4-qRjPLDeO16@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).