From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 90024385840C; Sat, 20 Jan 2024 20:45:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 90024385840C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1705783524; bh=qR9jRcUe94YbIQPrtC1t9ZxF8QiCKCznsnPZopnGGL4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=E1iULEoB8KudACl6NXxiobREW+JfjNBb4tYKGIzjt0IX15rAQBcqdBCuOCJhZsKX6 Xv0TuwUMKbQxzIzcefvZ3VzOfS5exUTfm4oewzMNSPV3C1sxoKpav3xejZwICqzs9Z bylIuJsQwIRNxg6mPnN0iIk8KwHyk5M17+BG6cZE= From: "jamborm 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: Sat, 20 Jan 2024 20:45:23 +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: jamborm at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94629 --- Comment #28 from Martin Jambor --- (In reply to David Binderman from comment #27) > The original article checked gcc-10. > gcc-13 is checked in the following article: >=20 > https://pvs-studio.com/en/blog/posts/cpp/1067/ >=20 > I suspect it would be most unwise if any release of gcc after 13=20 > introduced new bugs that were known to pvs-studio. And is there already a bugzilla bug about these (or should I create one)? I believe a new one would be better than re-using this one.=