loop unroll feedback

[Ian Lance Taylor]

Hoy Loper <hoy@loper.org> writes:

> I'm looking for something akin to PGI's -Minfo, that tells you a
> little bit about the thought process of the compiler as it optimizes.
> For example is there a way to know precisely where gcc unrolled your
> loops without looking at the binary code?

You could use -fdump-tree-all and look at the dump related passes.  In
some cases you can more information by adding -details.  See the docs on
-fdump-tree.

Ian