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/109350] FAIL: g++.dg/warn/Wstringop-overflow-4.C Date: Fri, 31 Mar 2023 06:35:38 +0000 [thread overview] Message-ID: <bug-109350-4-2OwPfLDvvp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109350-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109350 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Blocks| |88443 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- We have <bb 2> [local count: 1073741824]: _28 ={v} signed_value_source; _4 = (unsigned long) _28; _9 = _4 + 2147483648; if (_9 > 4294967295) goto <bb 8>; [50.00%] else goto <bb 3>; [50.00%] <bb 3> [local count: 536870913]: r_imin_imax_8 = (int) _28; _31 = r_imin_imax_8 + 1; _29 = (sizetype) _31; if (_4 <= 4611686018427387900) goto <bb 4>; [50.00%] else goto <bb 5>; [50.00%] <bb 5> [local count: 268435458]: _13 = operator new [] (18446744073709551615); __builtin_memcpy (_13, &MEM <const char[37]> [(void *)"0123456789abcdefghijklmnopqrstuvwxyz" + 35B], 2); sink (_13); if (_29 <= 4611686018427387900) goto <bb 9>; [100.00%] else goto <bb 7>; [0.00%] <bb 9> [local count: 0]: iftmp.1_38 = _29 * 2; _40 = operator new [] (iftmp.1_38); __builtin_memcpy (_40, &MEM <const char[37]> [(void *)"0123456789abcdefghijklmnopqrstuvwxyz" + 34B], 3); and we're again down into get_size_range of the operator new[] argument iftmp.1_38: pointer-query.cc:507 /* Determine the largest valid range size, including zero. */ if (!get_size_range (qry, size, stmt, r, SR_ALLOW_ZERO | SR_USE_LARGEST)) return NULL_TREE; where we compute [irange] long unsigned int [0, 0] NONZERO 0x0$27 = void for the range. I have to make up my mind if that's correct, but ranger debug prints the same conclusion so it doesn't seem to be an artifact of using legacy value_range. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 [Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
next prev parent reply other threads:[~2023-03-31 6:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-31 6:09 [Bug tree-optimization/109350] New: " rguenth at gcc dot gnu.org 2023-03-31 6:35 ` rguenth at gcc dot gnu.org [this message] 2023-03-31 7:17 ` [Bug tree-optimization/109350] " rguenth at gcc dot gnu.org 2023-03-31 14:30 ` amacleod at redhat dot com 2023-03-31 20:47 ` amacleod at redhat dot com
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-109350-4-2OwPfLDvvp@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).