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 5FD4C3984042; Fri, 29 May 2020 15:40:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5FD4C3984042
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1590766855;
 bh=n78V7r+0ekYNyMMCHucftHc3Tjk+vVljldFv2Bvy9oQ=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=kXFJsw4NrzrJb6NV+p1OBsufoONqIt+O4rM+wjwgnLtDDjRTBmbODgw/3aN6TZf96
 lNKb7nOUPo9SU5Vm1k+zNL6SSZKDHZbrPVfMhs/fyiWvhiO0xZw4m9Ew5SlPscNkl9
 SP8oRQwV2y5yQyorpOvQBqbIZznoA+/UGK4S4qdI=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/95348] GCC records zero functions and modules in
 the profiling data file, ICC does NOT
Date: Fri, 29 May 2020 15:40:55 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-95348-4-CiPJP39lh6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95348-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95348-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2020 15:40:55 -0000

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

--- Comment #11 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
(In reply to qinzhao from comment #9)
> (In reply to Martin Li=C5=A1ka from comment #7)
> > 1) You should not generate profile data for each process to a different
> > folder, but rather merge it.
>=20
> not sure how to do this? can you provide more details on this approach?

If you have an instrumented binary and you run it multiple times, then each
exit of the application merges profile to existing .gcda files on a disk.

The only exception is a cross-profiling:
https://gcc.gnu.org/onlinedocs/gcc/Cross-profiling.html

where one can use GCOV_PREFIX environment variable to save .gcda files to a
separate location.

Do you use it? Or do you use any of -fprofile-dir options?

>=20
> > 2) I would like to know how long does one process run and what portion =
is
> > spent in merging (and dumping) of a profile.
> will try to get this info.=