public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crrodriguez at opensuse dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/111659] New: document that -Wstrict-flex-arrays depends on -ftree-vrp
Date: Mon, 02 Oct 2023 00:16:06 +0000 [thread overview]
Message-ID: <bug-111659-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111659
Bug ID: 111659
Summary: document that -Wstrict-flex-arrays depends on
-ftree-vrp
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: crrodriguez at opensuse dot org
Target Milestone: ---
For -Wstrict-flex-arrays to be useful -ftree-vrp must be on..which is not the
case when building with -Og or -O1 .
It will be nice for this to be documented everywhere this option is mentioned
so people do not bang their heads against the table like me wondering why Im
getting no warnings on obvious code.
next reply other threads:[~2023-10-02 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 0:16 crrodriguez at opensuse dot org [this message]
2023-10-02 0:34 ` [Bug middle-end/111659] " pinskia at gcc dot gnu.org
2023-10-02 0:35 ` pinskia at gcc dot gnu.org
2023-10-02 19:12 ` crrodriguez at opensuse dot org
2024-01-17 22:15 ` cvs-commit at gcc dot gnu.org
2024-01-17 22:17 ` sandra 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-111659-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: link
Be 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).