This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Storing optimization choices in an ELF section

From: ludo at gnu dot org (Ludovic Courtès)
To: gcc-help at gcc dot gnu dot org
Date: Fri, 02 Jun 2017 13:14:02 +0200
Subject: Re: Storing optimization choices in an ELF section
Authentication-results: sourceware.org; auth=none
References: <8737bjzxkf.fsf@gnu.org> <c3b07e8a-5e06-fcc5-1db9-a1db277d3dfe@redhat.com>

Hi,

Andrew Haley <aph@redhat.com> skribis:

> 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.

Yes (modulo issues such as finding a compact and stable representation I
suppose), and it would be a useful tool.

Ludo’.

References:
- Storing optimization choices in an ELF section
  - From: Ludovic Courtès
- Re: Storing optimization choices in an ELF section
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]