2009.10.29 03:54 "Re: [Tiff] Libtiff release soon, please advise", by Edward Lam

On Wed, 28 Oct 2009, Edward Lam wrote:

I only looked at what caught my eye on the list. Bug 2001 seems like important low hanging fruit to do before final release:

     http://bugzilla.maptools.org/show_bug.cgi?id=2001

I agree that these issues should be avoided, but don't think that -fno-strict-aliasing is the answer since it surely makes the code slower. I did fix many of the aliasing warnings. The CVS HEAD version only produces these from the library code:

>... <snip>...

That's fine if someone has/will look at these to determine if they're real problems. I haven't. :)

Several utilities produce such warnings, and particularly 'tiffcrop' in CVS HEAD spews lots of them.

It's probably easy to introduce unless we build with the extra -Wstrict-aliasing=2 compiler?

The libtiff from CVS branch-3-9 (which would be 3.9.2) produces no aliasing warnings from the library, and just a few warnings about uninitialized variables in some of the utilities.

Sorry, I had somehow mistakenly thought that we were looking at a 4.0 release. :embarrassed:

Can you please re-check your builds with CVS libtiff and see if you see similar results?

I'm not sure if this is directed to me in particular. I had not checked in the first place since my usual development platform is on Win64. I trust your results are correct. :)

Regards,

-Edward