[sword-devel] -O3 -g (was: GCC warnings)
Troy A. Griffitts
scribe at crosswire.org
Fri Dec 4 21:41:33 MST 2009
Yeah J, you're probably right. I suppose I might try to justify the
settings in usrinst.sh by saying that these are the normal settings for
"users" needing to build the library (usually developers). These are
the settings I use daily while I develop (no shared libs, with debug).
But I'm sure you're at least building with shared libs for your release
I guess if you have some mechanism to build both debug and non-debug
libs, then you probably have the answer as to how the -O3 flag is being
set. I have always thought -g and -O3 to be in conflict-- usually the
resulting code from -O3 is unintelligible while trying to trace through
in gdb, but I guess technically they aren't in conflict. I wonder if
the optimized code including debug (-g -O3) is just as fast as -O3
On Fri, 2009-12-04 at 20:20 -0800, Jonathan Marsden wrote:
> Troy A. Griffitts wrote:
> > OK, glad we found that. I have a question though. There is a
> > significant performance gain for many features of SWORD when
> > debugging is turned off (which also turns -O3 on). When you build
> > packages for public consumption, don't you turn debugging off?
> I simply use the set of options that upstream (you guys :) recommend for
> people building from source, which are those in usrinst.sh. And that
> enables debug by default. Unless I made a mistake translating the info
> in usrinst.sh into debian/rules -- I'll recheck.
> I don't see a release.sh or similar "here are the suggested options for
> a production release" tool in the tarball, and the INSTALL file
> specifically says that the options in usrinst.sh are "what we consider
> 'normal'". Is there other documentation somewhere contradicting this?
> Having I been doing this "wrong" all along?
> I suspect that disabling --enable-debug will make it impractical to
> generate the debug library package, and trying to do multiple
> ./configure runs with different options, one for the "production"
> library and one for the debug libs, could be more work than I'd like.
> I'll play more with these options...
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel