From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 43F283987007; Wed, 27 May 2020 14:13:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 43F283987007 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1590588820; bh=MSpHY+kjvFqc6jSigyJuGHQaVKmUJ4P+XlaQps//fyA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MGn5zUkegNQjQaTbDASjdoDxWFjIJSxLU/vrvxYg65JAU+3LrbVAUtot0NvFI0qr5 D8zZhI4d/ga8rdpgwQPGPugjBKr+INQR36lorVn/dqnkIorxwsPf3Qxd9fn9/Nu4c1 AAKJpIygbDKk2dlm2S6T0dwHUMRcUGoszPbiayNM= From: "qinzhao at gcc dot 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: Wed, 27 May 2020 14:13:39 +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: qinzhao at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED 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: 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: Wed, 27 May 2020 14:13:40 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95348 --- Comment #3 from qinzhao at gcc dot gnu.org --- (In reply to Martin Li=C5=A1ka from comment #2) > Thank you for the report. It's a known limitation Honza noticed me about. > Is the size problematic from size perspective or speed perspective? I think both size and speed. for the full execution of our application, the GCC's profiling data is too = big to out of the disk space.=20=20 at the same time, since we have to merge all the profiling data for differe= nt processes, the merging process take a long time due to so many profiling da= ta files.=20 > Have you tried compressing the gcda files? >=20 > Anyway, I'm going to work on that this stage1. thanks a lot. this is a high priority task for us.=