How does the gcc -g option affect performance?

[Daniel Berlin]

On Thu, 2005-03-03 at 15:19 +0100, Brian Budge wrote:
> Yes, there's a large performance penalty.  (1) most optimizations
> can't be done because they foo with the debug data, thereby hurting
> debuggability 

What?

-g will not change what optimizations are run, or code generated.
This is gcc policy.

> (2) bloated code is slow code.
> 
Not really. It won't be loaded into memory unless it's used.

> Normally I expect my code to run about an order of magnitude slower with -g.
> 
Then something is very very wrong.