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 72B2B3858D32; Sun, 21 Jan 2024 08:55:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 72B2B3858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705827315;
	bh=TAB2AB9Z9Fg6imSKFn2zQBaBGN6JVgrhcGOirah1nWg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pKUpyLSN1gqqOD0KZgqrGTMl6V7DEevzncGg1CVcxUoc0KCSNE4Rxr+TIIjKLcICP
	 rZx5o5WaZRoijJ2GprBDN6vezuNaEQPZEKMfvE29zQhQP4CoHXrxEdQPWbW8yNn2T7
	 DzuCiuMVruzJE6KSzPF9dW7n0WznM7DHrY45OgV4=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113528] gcc-13 meets PVS-studio
Date: Sun, 21 Jan 2024 08:55:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: <bug-113528-4-imyXWGi3Vk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113528-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113528-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=3D113528

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>Fragment N6

So in the tools GCC's code that currenly use gcov_read_profile_dir is not a
leak that matters because the program exits if that fails. So it is only an
issue if someone externally uses it.=