This is the mail archive of the gcc-help@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: Debugging information slowdown?


Heitzso <heitzso@growthmodels.com> 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 Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]