public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/97048] [meta-bug] bogus/missing -Wstringop-overread warnings
Date: Fri, 31 Mar 2023 11:36:18 +0000 [thread overview]
Message-ID: <bug-97048-4-WqdPlFkBZ3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97048-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97048
Bug 97048 depends on bug 107087, which changed state.
Bug 107087 Summary: [12/13 Regression] bits/stl_algobase.h:431: warning: 'void* __builtin_memcpy(void*, const void*, unsigned int)' reading between 8 and 2147483644 bytes from a region of size 4 [-Wstringop-overread]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107087
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
next prev parent reply other threads:[~2023-03-31 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 16:23 [Bug middle-end/97048] New: " msebor at gcc dot gnu.org
2020-09-14 16:24 ` [Bug middle-end/97048] [meta-bug] " msebor at gcc dot gnu.org
2020-09-14 19:24 ` msebor at gcc dot gnu.org
2020-09-14 19:28 ` msebor at gcc dot gnu.org
2021-11-12 19:53 ` msebor at gcc dot gnu.org
2022-04-12 21:14 ` redi at gcc dot gnu.org
2022-12-20 0:06 ` msebor at gcc dot gnu.org
2022-12-20 10:13 ` roman.zilka at gmail dot com
2023-03-28 13:26 ` rguenth at gcc dot gnu.org
2023-03-31 11:36 ` rguenth at gcc dot gnu.org [this message]
2023-05-16 17:18 ` tonyguil at gmail dot com
2023-05-16 17:28 ` redi at gcc dot gnu.org
2023-05-17 10:14 ` tonyguil at gmail dot com
2023-06-01 15:11 ` redi 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-97048-4-WqdPlFkBZ3@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).