From: Patrick Herbst <paherbst@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: how does -Wstringop-truncation work?
Date: Mon, 30 Jan 2023 18:16:37 -0500 [thread overview]
Message-ID: <CACMdL5+KmADNhOKyHkTh1cSxL4pkKc=QCdmRMRRnZqJmN2m4OQ@mail.gmail.com> (raw)
In-Reply-To: <20230130230959.GW25951@gate.crashing.org>
On Mon, Jan 30, 2023 at 6:12 PM Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> The manual says
> The effectiveness of some warnings depends on optimizations also being
> enabled. For example '-Wsuggest-final-types' is more effective with
> link-time optimization and some instances of other warnings may not be
> issued at all unless optimization is enabled. While optimization in
> general improves the efficacy of control and data flow sensitive
> warnings, in some cases it may also cause false positives.
>
>
> Flags like -O1 do more than just enabling some other flags.
>
Thank you!
Another point of clarification; how is it that -foptimize-strlen is
necessary for -Wstringop-truncation to work? Is that noted somewhere?
next prev parent reply other threads:[~2023-01-30 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 22:35 Patrick Herbst
2023-01-30 23:09 ` Segher Boessenkool
2023-01-30 23:16 ` Patrick Herbst [this message]
2023-01-30 23:36 ` Jonathan Wakely
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='CACMdL5+KmADNhOKyHkTh1cSxL4pkKc=QCdmRMRRnZqJmN2m4OQ@mail.gmail.com' \
--to=paherbst@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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).