public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/48558] -Warray-bounds fails to detect the out of bound array access Date: Mon, 11 Apr 2011 19:10:00 -0000 [thread overview] Message-ID: <bug-48558-4-t2NirG2fOt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48558-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48558 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2011-04-11 19:09:54 UTC --- A simple change from return &elf_howto_table[R_386_IRELATIVE]; to return elf_howto_table[R_386_IRELATIVE]; makes GCC to warn: [hjl@gnu-6 bfd]$ cat x.c enum bfd_reloc_code_real { BFD_RELOC_386_IRELATIVE }; typedef enum bfd_reloc_code_real bfd_reloc_code_real_type; typedef const struct reloc_howto_struct reloc_howto_type; struct reloc_howto_struct { unsigned int type; }; enum elf_i386_reloc_type { R_386_IRELATIVE = 42, }; static reloc_howto_type elf_howto_table[]= { { (unsigned) R_386_IRELATIVE } }; reloc_howto_type elf_i386_reloc_type_lookup (bfd_reloc_code_real_type code) { switch (code) { case BFD_RELOC_386_IRELATIVE: return elf_howto_table[R_386_IRELATIVE]; default: break; } return elf_howto_table[0]; } [hjl@gnu-6 bfd]$ /usr/gcc-4.7.0-x32/bin/gcc -O3 -S -Wall x.c -Warray-bounds x.c: In function ‘elf_i386_reloc_type_lookup’: x.c:25:29: warning: array subscript is above array bounds [-Warray-bounds] [hjl@gnu-6 bfd]$
next prev parent reply other threads:[~2011-04-11 19:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-11 18:24 [Bug middle-end/48558] New: -Warray-bounds fails o " hjl.tools at gmail dot com 2011-04-11 18:40 ` [Bug middle-end/48558] -Warray-bounds fails to " hjl.tools at gmail dot com 2011-04-11 19:10 ` hjl.tools at gmail dot com [this message] 2011-04-12 10:28 ` 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-48558-4-t2NirG2fOt@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).