Re: [Gimp-developer] Why doesn't --enable-debug turn off optimization?
On Thursday 15 April 2010 18:56:53 Omari Stephens wrote: > 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. Shouldn't whoever says --enable-debug be able to say -O0 as well? Otherwise it might be harder to pin down erratic behaviour to the compiler. Daniel signature.asc Description: This is a digitally signed message part. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 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 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] 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 ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer