This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Storing optimization choices in an ELF section
- From: Andrew Haley <aph at redhat dot com>
- To: Ludovic Courtès <ludo at gnu dot org>, gcc-help at gcc dot gnu dot org
- Date: Thu, 1 Jun 2017 21:55:30 +0100
- Subject: Re: Storing optimization choices in an ELF section
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=aph at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 83DA485A07
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 83DA485A07
- References: <8737bjzxkf.fsf@gnu.org>
On 01/06/17 13:45, Ludovic Courtès wrote:
> A proprietary compiler stores information about optimizations it has
> made (loop unrolling, vectorization, etc.) in a ‘.debug_opt_report’ ELF
> section. This information can later be exploited by performance
> analysis tools, which can help understand performance.
>
> Has there been any thought on implementing something similar in GCC?
It's all in the -fverbose-asm output. It would be almost trivial
to output that into a .debug_opt_report section.
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671