AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2010.06.17 22:10 "[Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam
2010.06.18 02:38 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Bob Friesenhahn
2010.06.18 13:18 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam
2010.06.18 14:16 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Olivier Paquet
2010.06.21 21:20 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam
2010.06.21 23:05 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Adam Goode
2010.06.18 18:39 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Bob Friesenhahn
2010.06.28 13:22 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam
2010.06.29 17:12 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Albert Cahalan
2010.06.29 18:15 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam
2010.06.29 18:20 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam
2010.06.29 19:16 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Bob Friesenhahn

2010.06.18 14:16 "Re: [Tiff] libtiff 4.0 compiler warning on x64 in tif_read.c", by Olivier Paquet

On Fri, Jun 18, 2010 at 9:18 AM, Edward Lam <edward@sidefx.com> wrote:

I could go and just do blind type changes from int to tmsize_t until the

I wouldn't do it blindly just yet but it looks like both instances of read_ahead in there should have been tmsize_t.

compiler is satisfied but that's just a losing battle if we keep adding new code that has such warnings. Is there some gcc flag we can add to make it NOT compile such code?

Perhaps so for 64-bit gcc (couldn't find it though) but I don't think anything can be done if the author is working on a 32-bit system where there is nothing to warn about. We just have to deal with the fact that different compilers emit different sets of warnings.

Incidentally, what do we do for Windows? When new code is committed into libtiff, how do we even know that it builds under Windows? We can

We don't unless we try and build it. Nor can we ever be certain that it builds for every compiler/OS/configuration we're supposed to support.

certainly make it so that at least the Windows compiler treats these warnings as errors.

While I agree warnings should be fixed whenever possible, this seems counterproductive. It will simply cause libtiff to break all the time.

Olivier