From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Krishna Narayanan <krishnanarayanan132002@gmail.com>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Extended doubt regarding the bug 93432
Date: Wed, 9 Feb 2022 10:59:21 -0600 [thread overview]
Message-ID: <20220209165921.GN614@gate.crashing.org> (raw)
In-Reply-To: <CAH6eHdRH9-DnTexpGYWDjqDeBKD375e8gmvzoHPSvDKCVtMy1Q@mail.gmail.com>
On Tue, Feb 08, 2022 at 05:37:12PM +0000, Jonathan Wakely via Gcc-help wrote:
> It warns with -O1, which is the documented behaviour:
>
> The effectiveness of some warnings depends on optimizations also
> being enabled. For example -Wsuggest-final-types is more
> effective with link-time optimization and -Wmaybe-uninitialized does
> not warn at all unless optimization is enabled.
>
> So no, I don't think it' a bug. GCC is behaving as designed. Ideally it
> would be better at warning without optimization, but changing that would be
> hard.
GCC does not execute most of its code at -O0. This is important for
speed of course, but much more importantly it also allows us to use -O0
when other optimisation levels crash or generate wrong code. This is
useful for the compiler developers of course, but it also is an
important workaround for users, when bad things happen.
Segher
next prev parent reply other threads:[~2022-02-09 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 16:24 Krishna Narayanan
2022-02-08 16:58 ` Jonathan Wakely
2022-02-08 17:17 ` Krishna Narayanan
2022-02-08 17:37 ` Jonathan Wakely
2022-02-08 17:47 ` Krishna Narayanan
2022-02-08 21:50 ` Martin Sebor
2022-02-09 5:06 ` Krishna Narayanan
2022-02-11 18:10 ` Krishna Narayanan
2022-02-14 15:24 ` Martin Sebor
[not found] ` <CABhGnjvSO8svWrBNiO3aKJDjZ5mx2pE-kKgH-0pmyBYjLTwBRw@mail.gmail.com>
2022-02-14 20:22 ` Martin Sebor
2022-02-15 12:10 ` Krishna Narayanan
2022-02-16 21:27 ` Martin Sebor
2022-02-19 13:38 ` Krishna Narayanan
2022-02-09 16:59 ` Segher Boessenkool [this message]
2022-02-09 18:43 ` Krishna Narayanan
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=20220209165921.GN614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=krishnanarayanan132002@gmail.com \
/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).