[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: findings on swig-java-bindings

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-03-16 01:10:14 CET

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?

-- 
Philip Martin
---------------------------------------------------------------------
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:10:30 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.