public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of an array Date: Wed, 10 Feb 2021 20:28:51 +0000 [thread overview] Message-ID: <bug-95140-4-LGHhbnLzQk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95140-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95140 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11 Regression] bogus |[10/11 Regression] bogus |-Wstringop-overflow for a |-Wstringop-overflow for a |loop unrolled past the end |loop unrolled past the end |of a trailing array |of an array --- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> --- The problem isn't specific to trailing arrays; it can be reproduced with an interior member as well: $ gcc -O3 -S -Wall pr95140.cpr95140.c: In function ‘f’: pr95140.c:9:13: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] 9 | p->v[i] = s[i]; | ~~~~~~~~^~~~~~ pr95140.c:3:8: note: at offset 8 into destination object ‘v’ of size 8 3 | char v[8], u; | ^ ... pr95140.c:9:13: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] 9 | p->v[i] = s[i]; | ~~~~~~~~^~~~~~ pr95140.c:3:8: note: at offset 14 into destination object ‘v’ of size 8 3 | char v[8], u; | ^
next prev parent reply other threads:[~2021-02-10 20:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-14 19:19 [Bug middle-end/95140] New: [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array msebor at gcc dot gnu.org 2020-05-14 19:21 ` [Bug middle-end/95140] " msebor at gcc dot gnu.org 2020-05-14 19:24 ` msebor at gcc dot gnu.org 2020-05-14 19:25 ` jakub at gcc dot gnu.org 2020-05-14 20:30 ` msebor at gcc dot gnu.org 2020-05-15 7:23 ` rguenth at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-02-10 20:28 ` msebor at gcc dot gnu.org [this message] 2021-04-08 12:02 ` [Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of an array rguenth at gcc dot gnu.org 2022-01-09 22:30 ` [Bug tree-optimization/95140] [10/11/12 " pinskia at gcc dot gnu.org 2022-06-28 10:40 ` [Bug tree-optimization/95140] [10/11/12/13 " jakub at gcc dot gnu.org 2023-07-07 10:37 ` [Bug tree-optimization/95140] [11/12/13/14 " rguenth 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-95140-4-LGHhbnLzQk@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).