Re: Debugging information slowdown?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Heitzso <heitzso@xxxxxxxxxxxxxxxx> writes:

> Someone please correct me if I'm wrong, but in a common
> debugging situation optimizing is often turned off in order to
> have the generated code match original code a little better,
> i.e. stepping through the generated code makes more sense.
> But turning off all optimizing slows the code down.
> 
> Adding the -g introduces additional information to link
> variables/location back to the original code which makes
> the resultant code larger.

If I understand what you said correctly, you are wrong.

The -g option does not change the generated code at all.

It is certainly true that if you turn off optimization, the code will
change.

Ian

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux