public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tonyguil at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/97048] [meta-bug] bogus/missing -Wstringop-overread warnings Date: Tue, 16 May 2023 17:18:30 +0000 [thread overview] Message-ID: <bug-97048-4-yFoWhpMEZu@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 Tony Guilfoyle <tonyguil at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tonyguil at gmail dot com --- Comment #1 from Tony Guilfoyle <tonyguil at gmail dot com> --- Source file foo.cpp: #include <vector> struct T { void* p ; std::vector<char> a[10] ; } ; void f (T& t, const std::vector<char>& u, int i) { std::vector<char>& v = t.a[i] ; std::vector<char> w (u.begin(), u.end()) ; v.resize (v.size() - w.size()) ; // <-- Warning generated here } Command line: g++ -std=c++20 -Wall -O3 -c -o foo.obj foo.cpp g++ --version: g++.exe (MinGW-W64 x86_64-ucrt-posix-seh, built by Brecht Sanders) 12.2.0 Problem: Spurious warning emitted: specified bound between 9223372036854775808 and 18446744073709551614 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
next prev parent reply other threads:[~2023-05-16 17:18 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 2023-05-16 17:18 ` tonyguil at gmail dot com [this message] 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-yFoWhpMEZu@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: linkBe 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).