public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lehua.ding at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111211] No warning for iterator going out of scope Date: Mon, 28 Aug 2023 07:44:55 +0000 [thread overview] Message-ID: <bug-111211-4-nmVJ5lEIw5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111211-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111211 --- Comment #1 from Lehua Ding <lehua.ding at rivai dot ai> --- Reproduce: Compile Command: gcc -O3 -Wall -Wextra C Code: ``` #include <stdint.h> int foo (uint64_t ddr0_addr_access) { uint64_t check[1] = {0}; for (int k = 0; k < 7; k += 1) { asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); } return 0; } int foo2 (uint64_t ddr0_addr_access) { uint64_t check[1] = {0}; for (int k = 0; k < 8; k += 1) { asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); } return 0; } ``` Output: <source>: In function 'foo': <source>:9:41: warning: array subscript 1 is above array bounds of 'uint64_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds=] 9 | asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); | ~~~~~^~~ <source>:5:14: note: while referencing 'check' 5 | uint64_t check[1] = {0}; | ^~~~~ <source>:9:41: warning: array subscript 2 is above array bounds of 'uint64_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds=] 9 | asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); | ~~~~~^~~ <source>:5:14: note: while referencing 'check' 5 | uint64_t check[1] = {0}; | ^~~~~ <source>:9:41: warning: array subscript 3 is above array bounds of 'uint64_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds=] 9 | asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); | ~~~~~^~~ <source>:5:14: note: while referencing 'check' 5 | uint64_t check[1] = {0}; | ^~~~~ <source>:9:41: warning: array subscript 4 is above array bounds of 'uint64_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds=] 9 | asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); | ~~~~~^~~ <source>:5:14: note: while referencing 'check' 5 | uint64_t check[1] = {0}; | ^~~~~ <source>:9:41: warning: array subscript 5 is above array bounds of 'uint64_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds=] 9 | asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); | ~~~~~^~~ <source>:5:14: note: while referencing 'check' 5 | uint64_t check[1] = {0}; | ^~~~~ <source>:9:41: warning: array subscript 6 is above array bounds of 'uint64_t[1]' {aka 'long unsigned int[1]'} [-Warray-bounds=] 9 | asm volatile ("nop" : "=r"(check[k]) : "r"(ddr0_addr_access)); | ~~~~~^~~ <source>:5:14: note: while referencing 'check' 5 | uint64_t check[1] = {0}; | ^~~~~ Compiler returned: 0
next prev parent reply other threads:[~2023-08-28 7:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-28 7:42 [Bug c/111211] New: " lehua.ding at rivai dot ai 2023-08-28 7:44 ` lehua.ding at rivai dot ai [this message] 2023-08-28 9:27 ` [Bug c/111211] " rguenth at gcc dot gnu.org 2023-08-28 9:30 ` lehua.ding at rivai dot ai 2023-08-28 13:13 ` pinskia at gcc dot gnu.org 2023-08-28 13:54 ` [Bug tree-optimization/111211] No warning for iterator going out of scope for writing to array of inline-asm 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-111211-4-nmVJ5lEIw5@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).