[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-17 19:13:44 CET

"Gustav Munkby" <grddev@gmx.net> writes:

> Since it's really a problem with gcc3 trying to apply inapplicable
> optimizations, I think it should be dealt as such and therefore the
> best option available would be to actually use -fno-strict-aliasing.

Are you saying that you know the warning is a false alarm? Can you
provide some justification.

If it's not a false alarm then it's not a gcc3 problem either and
adding -fno-strict-aliasing would be simply hiding the problem. gcc
is warning us that *any* C99 compiler is allowed to make these
optimisations. Yes, adding -fno-strict-aliasing will stop gcc making
the optimisations, but it provides no guarantee that some other
compiler won't make the same assumptions and so optimise it.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 19:14:07 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.