From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A4644385DC04; Fri, 17 Apr 2020 09:14:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A4644385DC04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1587114857; bh=Zvg+FG6q27Uppzp5PSn1ubA6YbcuePvBQGv+Bn/e4gA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=DXaGSKfgR7QImWAcame9WCnCi50QT1QpXUCyHS58AkXKmNUvgCgBo570VDQmWkQt1 NDmMyNKakkTQwbpYrV+EaOUKIdIzvWuAivk1z2GFqY7leZJZJxQXO4Hzxul2bNeFY7 aW/l3H8FJ7zedcr1LVU/55PRd13u803G6jl7wu7w= From: "jakub 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 09:14:17 +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: jakub 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: cc 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 09:14:17 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94629 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek --- We should for GCC11 discuss if we want to implement some of these checks, either in -fanalyzer, or as normal GCC warnings. E.g. the foo =3D something; // code that can't affect foo foo =3D somethingelse; is perhaps something that should be warned as early as possible after getti= ng into GIMPLE, before inlining because it is quite common that inlines overwr= ite something, and in the FEs it is likely too early.=