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 39E783857C70; Tue, 11 Aug 2020 12:20:20 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 39E783857C70
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1597148420;
 bh=rJaZOmhogdhSGU0hlAjlZzA9Litkiq7BgkgaVUpK+mw=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=JBjh8uJhiJr9jtK0TO1TCmKz9ocfZtitZIjuNS0Kmrc/MiRGahV/nYRPwMYf4zm6b
 SRFL2WeBhP/Oe+AR1bkxER634zl9Rt/bMYrTh9t+6j+2otXcBJfcR5O3vQCOZi5sya
 FAPzwwFqUmmd5QIS/Wdx+SOG3taHVQEJJ1VtaboQ=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/96534] keep gcov intermediate format
Date: Tue, 11 Aug 2020 12:20:20 +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: 9.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-96534-4-qTU5i8AAK3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96534-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96534-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: <https://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: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 12:20:20 -0000

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

--- Comment #4 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
> I did not have the real statistics yet as our company is not yet moved to
> gcc9 (maybe end of this year ).
>=20
> and even the size of the compressed file is smaller , but we have to unzip
> and parse it , right? it just increase the workload .=20

Yes, but if it's problem we can start using e.g. zstd that has super-fast
decompression.

>=20
> however, the stdout option ( -t ) could be very helpful , we don't need to
> write to disk and just parse the stdout content.

Yes, that be quite useful for your test-case. Or you may consider using:
https://github.com/RPGillespie6/fastcov

>=20
> well, I also notice that the "function_name" in "lines" object is mangled
> even I use "--demangled-names" option, can you print the demangled_name w=
hen
> "-m" option given ? ( yes I know there is demangled name in "functions" p=
art
> ) . the reason is: we need to know the exact function name and it's lines,
> in current format , we have to find all demangled function name and it's
> start and end line number, then check the lines part to assign each lines
> into functions .

It's handy to use mangled name as a unique key from "lines" to "functions".=