Philip Martin wrote:
> Daniel Rall <dlr@collab.net> writes:
>
>
>>* build/ac-macros/swig.m4
>> (SWIG_JAVA_INCLUDES): Include the -fno-strict-aliasing argument to
>> gcc to disable the optimization which can generate build warnings.
>
>
> It's possible these warnings are false alarms, but if they are not
> then the code is broken, and it may get miscompiled by compilers other
> than gcc. If we hide the warnings in the normal development
> environment there is less incentive to fix the code, or even
> investigate if we really have a problem.
>
> On the other hand if gcc really is going to produce invalid object
> code from our invalid source code then it seems sensible to enable
> this for production. Perhaps this flag should only be added if
> enable-maintainer-mode is not used?
And whatever we do, it should be applied to the SWIG-based Python, Java, and
Perl bindings (and Perl is already using the -fno-strict-aliasing flag!).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 16 01:22:53 2004