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? (My googlefoo is not strong, so I'm sorry if I missed it somewhere.) -- Hoy