|--==> "JJ" == Jerry James <james(a)xemacs.org> writes:
JJ> Using any optimization setting at all causes it to link correctly. So
JJ> now the question becomes whether we should try to work around this bug
JJ> or not, and if so, how.
Is the optimisation only needed with '--error-checking=all' (on gcc)?
What consequences will arise from unconditionally turning on say '-O1'
if '--error-checking=all'? Would backtraces be affected
detrimentally?
If nothing's likely to blow up in our face I'd suggest if anyone uses
'--error-checking=all' then add '-O1' to the new cflags_warnings.
That way it won't be overridden by someone's $CFLAGS if they have it
set. What do you think?
In any event, it would probably be a good idea to add an entry to
PROBLEMS.
--
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|