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 middle-end/98503] [11/12 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da Date: Wed, 23 Mar 2022 08:31:54 +0000 [thread overview] Message-ID: <bug-98503-4-s2BYyWEG0G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98503-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98503 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #18 from Richard Biener <rguenth at gcc dot gnu.org> --- So at the point we diagnose we see the following IL for cont_dump: <bb 2> [local count: 1073741824]: __mptr_5 = MEM[(struct ref *)&head].list.n; goto <bb 8>; [100.00%] that's because the testcase has static 'last_dumped' which means it is NULL and we start restart_dump with if (!last) last = get_initial_step(); which does static inline struct ref *get_initial_step() { return container_of(&head, struct ref, list); } that means next_step will do the bad access of 'head' using the struct ref type.
next prev parent reply other threads:[~2022-03-23 8:31 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-03 7:53 [Bug c/98503] New: [11 regression] -Warray-bounds false positive with global variables at -O2 w at 1wt dot eu 2021-01-03 7:56 ` [Bug c/98503] " w at 1wt dot eu 2021-01-04 12:33 ` [Bug c/98503] [11 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da marxin at gcc dot gnu.org 2021-01-04 16:06 ` msebor at gcc dot gnu.org 2021-01-04 16:17 ` w at 1wt dot eu 2021-01-04 16:19 ` w at 1wt dot eu 2021-01-04 17:41 ` msebor at gcc dot gnu.org 2021-01-04 22:43 ` w at 1wt dot eu 2021-01-05 11:16 ` rguenth at gcc dot gnu.org 2021-01-05 11:34 ` w at 1wt dot eu 2021-01-05 17:31 ` msebor at gcc dot gnu.org 2021-01-28 23:06 ` [Bug middle-end/98503] " msebor at gcc dot gnu.org 2021-04-27 11:40 ` [Bug middle-end/98503] [11/12 " jakub at gcc dot gnu.org 2021-05-05 16:52 ` msebor at gcc dot gnu.org 2021-05-05 17:16 ` w at 1wt dot eu 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-11-17 22:34 ` msebor at gcc dot gnu.org 2022-03-08 0:03 ` msebor at gcc dot gnu.org 2022-03-23 8:31 ` rguenth at gcc dot gnu.org [this message] 2022-03-23 9:32 ` w at 1wt dot eu
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-98503-4-s2BYyWEG0G@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).