public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104355] New: Misleading -Warray-bounds documentation says "always out of bounds" Date: Wed, 02 Feb 2022 20:44:01 +0000 [thread overview] Message-ID: <bug-104355-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104355 Bug ID: 104355 Summary: Misleading -Warray-bounds documentation says "always out of bounds" Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: documentation Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- -Warray-bounds -Warray-bounds=n This option is only active when -ftree-vrp is active (default for -O2 and above). It warns about subscripts to arrays that are always out of bounds. This warning is enabled by -Wall. It's not true that it warns for "always out of bounds", as that implies no false positives.
next reply other threads:[~2022-02-02 20:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-02 20:44 redi at gcc dot gnu.org [this message] 2022-02-02 21:21 ` [Bug middle-end/104355] " pinskia at gcc dot gnu.org 2022-02-08 22:17 ` msebor at gcc dot gnu.org 2022-02-08 22:17 ` msebor at gcc dot gnu.org 2022-02-11 0:00 ` msebor at gcc dot gnu.org 2022-02-14 22:55 ` cvs-commit at gcc dot gnu.org 2024-01-19 4:34 ` sandra at gcc dot gnu.org 2024-01-20 17:18 ` 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-104355-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).