public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andres at anarazel dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104986] New: [12 Regression] bogus writing 1 byte into a region of size 0 with -fwrapv and -O2 -fpeel-loops Date: Sat, 19 Mar 2022 17:07:46 +0000 [thread overview] Message-ID: <bug-104986-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104986 Bug ID: 104986 Summary: [12 Regression] bogus writing 1 byte into a region of size 0 with -fwrapv and -O2 -fpeel-loops Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: andres at anarazel dot de Target Milestone: --- Hi, recently started seeing bogus warnings using gcc 12 to build postgres. I reduced the problem using cvise with some manual cleanups / improvements afterwards - certainly doesn't quite make sense anymore, but afaics shows a problem. Originally I hit this with -O3, but found that -O2 -fpeel-loops is sufficient to trigger the problem. repro: https://godbolt.org/z/ejK9h6von code: struct inet_struct { char family; char ipaddr[16]; }; void inetnot(struct inet_struct *dst1, struct inet_struct *dst2, struct inet_struct *src) { int nb = src->family ? 4 : 6; char *psrc = src->ipaddr; char *pdst = dst1 ? dst1->ipaddr : dst2->ipaddr; while (nb-- > 0) pdst[nb] = psrc[nb]; } gcc-12 -fwrapv -O2 -fpeel-loops -c network2.i network2.i: In function ‘inetnot’: network2.i:12:14: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] 12 | pdst[nb] = psrc[nb]; | ~~~~~~~~~^~~~~~~~~~ network2.i:3:8: note: at offset -1 into destination object ‘ipaddr’ of size 16 3 | char ipaddr[16]; | ^~~~~~ network2.i:3:8: note: at offset -1 into destination object ‘ipaddr’ of size 16 which afaics is bogus, because the loop terminates before reaching offset -1, the condition is > 0, not >= 0. So the post decrement can't lead to -1 being reached. version: gcc version 12.0.1 20220314 (experimental) [master r12-7638-g823b3b79cd2] (Debian 12-20220313-1) Regards, Andres
next reply other threads:[~2022-03-19 17:07 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-19 17:07 andres at anarazel dot de [this message] 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 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@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).