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 tree-optimization/105723] [12 Regression] Optimization false positive warning (-Wstringop-overflow)
Date: Tue, 21 Feb 2023 14:31:42 +0000 [thread overview]
Message-ID: <bug-105723-4-X3AgHCgUlO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105723-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105723
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[12/13 Regression] |[12 Regression]
|Optimization false positive |Optimization false positive
|warning |warning
|(-Wstringop-overflow) |(-Wstringop-overflow)
Last reconfirmed| |2023-02-21
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Known to work| |13.0
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed with GCC 12 but it seems that GCC 13 is no longer affected, possibly
due to standard library changes.
next prev parent reply other threads:[~2023-02-21 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 20:22 [Bug c++/105723] New: Optimization false positive warning jeffrey.reynolds at ticketmaster dot com
2022-05-25 7:34 ` [Bug libstdc++/105723] " rguenth at gcc dot gnu.org
2022-10-25 22:41 ` [Bug tree-optimization/105723] [12/13 Regression] Optimization false positive warning (-Wstringop-overflow) pinskia at gcc dot gnu.org
2023-02-21 14:31 ` rguenth at gcc dot gnu.org [this message]
2023-04-27 11:33 ` [Bug tree-optimization/105723] [12 " rguenth at gcc dot gnu.org
2023-05-01 9:54 ` sjames at gcc dot gnu.org
2023-05-01 13:12 ` pinskia at gcc dot gnu.org
2023-05-01 13:40 ` sjames 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-105723-4-X3AgHCgUlO@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).