From: Jakub Jelinek <jakub@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Report from the additional type errors for GCC 14 BoF at Cauldron
Date: Tue, 26 Sep 2023 11:22:07 +0200 [thread overview]
Message-ID: <ZRKiv/SDmLYc/74g@tucnak> (raw)
In-Reply-To: <87edilpcct.fsf@oldenburg.str.redhat.com>
On Tue, Sep 26, 2023 at 10:28:34AM +0200, Florian Weimer via Gcc wrote:
> My understanding of the consensus goes as follows:
>
> * We want to make some changes in this area for GCC 14.
> * We should do the same thing that Clang does: default to the relevant
> -Werror= options.
I think it doesn't have to be necessarily using defaulting to -Werror=,
-Werror= involves diagnostic_classify_diagnostic etc.
It could very well be also just testing if the corresponding warning
option isn't explicitly (OPTION_SET_P) disabled and isn't explicitly
-Wno-error=OPTION and c99 or later and conditionally based on that
use error (which would print the [-W...] part though) or warning.
The former would be in system headers too, the latter wouldn't.
We need to decide what exact options we want to turn those errors (and/or
warnings) off or on, -Wno-implicit-int, -w, -Wno-error,
-Wno-error=implicit-int, ...
Jakub
next prev parent reply other threads:[~2023-09-26 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 8:28 Florian Weimer
2023-09-26 9:22 ` Jakub Jelinek [this message]
2023-09-26 12:04 ` Florian Weimer
2023-09-26 12:22 ` Jeff Law
2023-09-26 13:42 ` Florian Weimer
2023-09-26 18:49 ` Sam James
2023-09-26 18:40 ` Sam James
2023-09-26 22:06 ` Arsen Arsenović
2023-09-27 4:44 ` Florian Weimer
2023-09-27 8:52 ` Anaya Shah
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=ZRKiv/SDmLYc/74g@tucnak \
--to=jakub@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc@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).