The purpose of --enable-debug-symbols was to produce an
_identical_ executable to the release version, but with symbols for
profiling. The --enable-optimized-debug is mostly optimized, but
not as much as the release version because it disables inline
functions. When profiling code for the purposes of optimization,
you want to know _exactly_ where the hot spots are in the release
build, because they will often be different in a debug build.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
created with "cvs diff -u"
Logged In: YES
user_id=23042
I just noticed we already have a --enable-optimized-debug
option that sets -g -O2 -fno-default-inline -fno-inline
Logged In: YES
user_id=770895
The purpose of --enable-debug-symbols was to produce an
_identical_ executable to the release version, but with symbols for
profiling. The --enable-optimized-debug is mostly optimized, but
not as much as the release version because it disables inline
functions. When profiling code for the purposes of optimization,
you want to know _exactly_ where the hot spots are in the release
build, because they will often be different in a debug build.