public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104986] [12 Regression] bogus writing 1 byte into a region of size 0 with -fwrapv and -O2 -fpeel-loops since r12-4698-gf6d012338bf87f42 Date: Wed, 23 Mar 2022 09:45:03 +0000 [thread overview] Message-ID: <bug-104986-4-ChUK02Ynzc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104986-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104986 Aldy Hernandez <aldyh at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amacleod at redhat dot com, | |siddhesh at gcc dot gnu.org --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- [Siddhesh, I don't know if this is something you're looking at. If not, feel free to unsubscribe.] This may have first been visible with r12-4698-gf6d012338bf87f42, but it isn't threader related as it can be reproduced with -fno-thread-jumps. I can actually reproduce it without VRP[12] (but not without evrp). + ./cc1 a.c -fdump-tree-all-details -quiet -I/tmp -O2 -fpeel-loops -fwrapv -fno-thread-jumps -fdisable-tr ee-vrp2 -fdisable-tree-vrp1 cc1: note: disable pass tree-vrp2 for functions in the range of [0, 4294967295] cc1: note: disable pass tree-vrp1 for functions in the range of [0, 4294967295] a.c: In function ‘inetnot’: a.c:12:14: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] etc etc Disabling evrp causes the problem to go away, but all these middle end warnings are very sensitive to better ranges, so who knows. For that matter, the only transformation evrp is doing is correct: @@ -74,7 +90,7 @@ <bb 9> : # nb_8 = PHI <iftmp.0_9(7), nb_23(8)> nb_23 = nb_8 + -1; - if (nb_8 > 0) + if (nb_8 != 0) goto <bb 8>; [INV] else goto <bb 10>; [INV] ...which is merely changing the conditional in the decreasing loop from > 0 into != 0. It looks like a problem elsewhere.
next prev parent reply other threads:[~2022-03-23 9:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-19 17:07 [Bug middle-end/104986] New: [12 Regression] bogus writing 1 byte into a region of size 0 with -fwrapv and -O2 -fpeel-loops andres at anarazel dot de 2022-03-21 8:53 ` [Bug middle-end/104986] " rguenth at gcc dot gnu.org 2022-03-21 9:31 ` [Bug middle-end/104986] [12 Regression] bogus writing 1 byte into a region of size 0 with -fwrapv and -O2 -fpeel-loops since r12-4698-gf6d012338bf87f42 marxin at gcc dot gnu.org 2022-03-23 9:45 ` aldyh at gcc dot gnu.org [this message] 2022-03-23 13:05 ` rguenth at gcc dot gnu.org 2022-03-23 14:45 ` aldyh at gcc dot gnu.org 2022-03-23 14:46 ` amacleod at redhat dot com 2022-03-23 14:49 ` aldyh at gcc dot gnu.org 2022-03-23 14:58 ` amacleod at redhat dot com 2022-03-23 15:05 ` rguenth at gcc dot gnu.org 2022-04-19 5:20 ` jakub at gcc dot gnu.org 2022-05-06 8:33 ` [Bug middle-end/104986] [12/13 " jakub at gcc dot gnu.org 2022-07-26 12:38 ` rguenth at gcc dot gnu.org 2023-05-08 12:24 ` [Bug middle-end/104986] [12/13/14 " rguenth at gcc dot gnu.org 2023-09-02 20:02 ` 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-104986-4-ChUK02Ynzc@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).