From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9C621385DC1C; Fri, 17 Apr 2020 12:08:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9C621385DC1C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587125289; bh=vQzAD6uCUgViIAVrQPwd9TalIeYtGv2m7PPAV6tR5oY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jBb2d3EKEMnjtybVUVDM3SeJX3VKXBhb2ZlEpkifCjLYeYcUkK1LYnqeIxL0LzVZp 8QR2zxTWMHvEl82UKMPAX7tH6GeanRJqUX4B6vnWFQ9FZGtawoFrjkd+c2KGfHZ43v Uy2L94HcGfwFfuMJk26NBlPaQoYGcz+Jdfsc2F3A= From: "ams at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/94629] 10 issues located by the PVS-studio static analyzer Date: Fri, 17 Apr 2020 12:08:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ams at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: In-Reply-To: References: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Apr 2020 12:08:09 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94629 --- Comment #11 from Andrew Stubbs --- (In reply to Jakub Jelinek from comment #10) > or if instead we should drop the "status =3D " for the cases where nothing > checks it. Andrew? I think checking the status is probably good practice, even though I don't think there's an actual bug here.=