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/109791] -Wstringop-overflow warning with -O3 and _GLIBCXX_USE_CXX11_ABI=0 Date: Thu, 25 May 2023 12:14:29 +0000 [thread overview] Message-ID: <bug-109791-4-JDAruIxMaY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109791-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109791 --- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> --- So one issue with the unfolding of PHIs is that for example gcc.dg/warn-sprintf-no-nul.c has const char a2[][3] = { "", "1", "12", "123", "123\000" }; and for # str_1 = PHI <&a2[2], &a2[3]> we can determine bounds on the string length of str_1 by unioning the string lengths of &a2[2] and &a2[3]. But with # off_2 = PHI <6, 9> str_1 = &a2 + off_2; this isn't possible. In fact get_range_strlen doesn't handle POINTER_PLUS_EXPR and while it might be possible to handle "foo" + off_2 with looking at the range of off_2 for example the above case of refering to two different strings rather than offsetting within one string isn't distinguishable. I've also figured that when one PHI argument has zero offset (aka plain &a2) then PRE tends to undo the transform since &a2 + 0 is readily available on that edge and thus it inserts pointer adjustments on the other edges. So while it looked like the easy way out on the ranger limitation it's not a viable solution (because it regresses testcases).
next prev parent reply other threads:[~2023-05-25 12:14 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-09 16:48 [Bug c++/109791] New: " szhong at perforce dot com 2023-05-09 17:28 ` [Bug tree-optimization/109791] " pinskia at gcc dot gnu.org 2023-05-10 7:26 ` rguenth at gcc dot gnu.org 2023-05-11 8:05 ` aldyh at gcc dot gnu.org 2023-05-11 8:19 ` aldyh at gcc dot gnu.org 2023-05-11 9:39 ` rguenth at gcc dot gnu.org 2023-05-11 9:47 ` aldyh at gcc dot gnu.org 2023-05-11 11:36 ` rguenther at suse dot de 2023-05-11 11:40 ` rguenth at gcc dot gnu.org 2023-05-11 12:22 ` rguenth at gcc dot gnu.org 2023-05-11 12:34 ` rguenth at gcc dot gnu.org 2023-05-11 12:35 ` rguenth at gcc dot gnu.org 2023-05-11 12:36 ` rguenth at gcc dot gnu.org 2023-05-12 11:48 ` cvs-commit at gcc dot gnu.org 2023-05-25 12:14 ` rguenth at gcc dot gnu.org [this message] 2023-05-25 12:15 ` rguenth at gcc dot gnu.org 2023-05-25 12:16 ` rguenth at gcc dot gnu.org 2023-05-25 15:35 ` pinskia at gcc dot gnu.org 2023-06-07 22:28 ` 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-109791-4-JDAruIxMaY@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).