From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 77ECC3858005; Fri, 12 Jan 2024 19:51:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 77ECC3858005
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705089115;
	bh=vw3t3847nX4jy+y6GKY4aXy4aDu7mUt0KgP5JphSA7U=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=NNnUtIjYkQ6NR89R/5NqthZJNJVe9APRXH8ayrvmsX+wL+BsDi/jCrNLKcd6++zHZ
	 /9/IIkq6kHbbq5UpMvn6DHoFi3++39uN1Dt+fyHWckeYIAT8dzMioR8yYDwVwFRm2K
	 AjY66ilL9QDM3Dofty5tExlGP+zvtikXokwxizgI=
From: "segher 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 19:51:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-89072-4-Vhfe6FZtNt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D89072

--- Comment #11 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #9)
> 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.

Sure.  If people want the pain, they can have it.  But it is never okay to
cause other people to have -Werror -- they may have a different compiler
(version) that no one else has tested with, they may have different warnings
enabled, etc.

> But enabling any kind of -Werror by default is always wrong.

Yup.=