RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Why doesn't --enable-debug turn off optimization?

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 3 messages available
Toggle history

Please log in to manage your subscriptions.
Why doesn't --enable-debug turn off optimization? Omari Stephens 15 Apr 18:56
  Why doesn't --enable-debug turn off optimization? Oliver Bandel 16 Apr 00:42
  201004160128.29144.daniel.h... Daniel Hornung 16 Apr 01:28
Omari Stephens
2010-04-15 18:56:53 UTC (about 15 years ago)

Why doesn't --enable-debug turn off optimization?

It seems like running configure with --enable-debug should also disable optimization; otherwise you end up with a bunch of magically inlined or optimized-out function calls, optimized-out variables, and confusing execution order.

Thoughts?

--xsdg

Oliver Bandel
2010-04-16 00:42:25 UTC (about 15 years ago)

Why doesn't --enable-debug turn off optimization?

Zitat von "Omari Stephens" :

It seems like running configure with --enable-debug should also disable optimization; otherwise you end up with a bunch of magically inlined or optimized-out function calls, optimized-out variables, and confusing execution order.

Thoughts?

[...]

AFAIK gcc inlines starting with -O3 and higher.

I'm not sure what happens with optimizations with less than -O3, but maybe the result is not that extremely chaotic.

Completely disabling optimizations would make sure that debugging might be possible easily.

Ciao, Oliver