public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Fri, 12 May 2023 11:48:40 +0000 [thread overview] Message-ID: <bug-109791-4-3LaojbLy65@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 #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:560a3e35fe01c499bd5b1e95ddc4c3e958cf5abd commit r14-785-g560a3e35fe01c499bd5b1e95ddc4c3e958cf5abd Author: Richard Biener <rguenther@suse.de> Date: Thu May 11 14:28:11 2023 +0200 tree-optimization/109791 - simplify (unsigned)&foo - (unsigned)(&foo + o) The following adds another variant of address difference simplification. The utility ptr_difference_const only handles constant differences (we also cannot code generate anything else), so exposing a possible POINTER_PLUS_EXPR in the match and computing the difference on the base only makes it possible to handle one case of a variable offset. This simplifies (unsigned long) &MEM <char[3]> [(void *)&str + 2B] - (unsigned long) (&str + (_69 + 1)) down to (1 - (unsigned long) _69) during niter analysis, allowing ranger to eliminate a condition later and avoiding a bogus -Wstringop-overflow diagnostic for the testcase in the PR. PR tree-optimization/109791 * match.pd (minus (convert ADDR_EXPR@0) (convert (pointer_plus @1 @2))): New pattern. (minus (convert (pointer_plus @1 @2)) (convert ADDR_EXPR@0)): Likewise.
next prev parent reply other threads:[~2023-05-12 11:48 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 [this message] 2023-05-25 12:14 ` rguenth at gcc dot gnu.org 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-3LaojbLy65@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).