This is the mail archive of the gcc@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: GCC optimization report

From: Tim Prince <n8tm at aol dot com>
To: gcc at gcc dot gnu dot org
Date: Tue, 17 Jul 2012 10:49:06 -0400
Subject: Re: GCC optimization report
References: <M7AWGM$03F7F9AF87C453EB107C39FFD0515E2D@libero.it> <CAFiYyc1_b57hEe-9oN92EjJBKUQ+_ZVyWbMjF2PejOC9igtSnw@mail.gmail.com>
Reply-to: tprince at computer dot org

On 7/17/2012 7:23 AM, Richard Guenther wrote:

On Tue, Jul 17, 2012 at 12:43 PM,<Erotavlas_turbo@libero.it> wrote:

Hi all,
I would like to know if GCC provides an option to get a detailed report on the optimization actually performed by the compiler. For example with the Intel C compiler it is possible using the -opt-report. I don't want to look at the assembly file and figure out the optimization.

There is only -ftree-vectorizer-verbose=N currently and the various dump-files
the individual passes produce (-fdump-tree-all[-subflags]
-fdump-rtl-all[-subflags]).

-ftree-vectorizer-verbose is analogous to the icc -vec-report option (included in -opt-report). Among the questions not answered by -opt-report are those associated with application (or not) of -complex-limited-range (gcc -fcx-limited-range). -opt-report3 I believe turns on reporting of software prefetch application, which is important but difficult to follow. It's nearly impossible to compare icc and gcc optimization other than by examining assembly and using a profiler which shows paths taken.

--
Tim Prince

References:
- GCC optimization report
  - From: Erotavlas_turbo
- Re: GCC optimization report
  - From: Richard Guenther

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