public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109716] bogus stringop-overread "reading 4 bytes from a region of size 0"
Date: Wed, 03 May 2023 18:09:44 +0000 [thread overview]
Message-ID: <bug-109716-4-mQDjAZub3G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109716-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109716
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |97048
Component|c |tree-optimization
Last reconfirmed| |2023-05-03
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
Keywords| |diagnostic
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you attach the preprocessed source as requested on
https://gcc.gnu.org/bugs/ ?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97048
[Bug 97048] [meta-bug] bogus/missing -Wstringop-overread warnings
next prev parent reply other threads:[~2023-05-03 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:36 [Bug c/109716] New: " david at ixit dot cz
2023-05-03 18:09 ` pinskia at gcc dot gnu.org [this message]
2023-05-04 18:42 ` [Bug tree-optimization/109716] " david at ixit dot cz
2023-05-04 18:47 ` [Bug tree-optimization/109716] mesa/r300 " pinskia at gcc dot gnu.org
2023-05-04 19:10 ` pinskia 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-109716-4-mQDjAZub3G@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).