public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89072] -Wall -Werror should be defaults
Date: Fri, 12 Jan 2024 15:51:37 +0000 [thread overview]
Message-ID: <bug-89072-4-6Cs89r42xp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89072
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It is not always wrong, it is a reasonable choice for some projects during
their development, if they are willing to fix or work around all new warnings,
even if they are false positives.
But enabling any kind of -Werror by default is always wrong.
next prev parent reply other threads:[~2024-01-12 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-89072-4@http.gcc.gnu.org/bugzilla/>
2024-01-12 13:33 ` xry111 at gcc dot gnu.org
2024-01-12 14:36 ` segher at gcc dot gnu.org
2024-01-12 15:06 ` vincent-gcc at vinc17 dot net
2024-01-12 15:08 ` vincent-gcc at vinc17 dot net
2024-01-12 15:18 ` segher at gcc dot gnu.org
2024-01-12 15:44 ` xry111 at gcc dot gnu.org
2024-01-12 15:51 ` jakub at gcc dot gnu.org [this message]
2024-01-12 15:58 ` mpolacek at gcc dot gnu.org
2024-01-12 19:51 ` segher at gcc dot gnu.org
2024-01-12 22:38 ` vincent-gcc at vinc17 dot net
2024-01-13 18:57 ` segher at gcc dot gnu.org
2024-01-15 4:03 ` egallager 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-89072-4-6Cs89r42xp@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).