AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
June 2010

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

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

2010.06.18 18:39 "Re: libtiff 4.0 compiler warning on x64 in tif_read.c", by Bob Friesenhahn

On Fri, 18 Jun 2010, Edward Lam wrote:
>
> I could go and just do blind type changes from int to tmsize_t until the 
> 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?

GCC is one of the least useful compilers for reporting such issues.

> 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 certainly 
> make it so that at least the Windows compiler treats these warnings as 
> errors.

I am not sure.  From time to time I compile under Windows using the 
MinGW compiler since it is most convenient for me.  It is not clear to 
me that any of the libtiff maintainers are using MSVC to regularly 
build libtiff under Windows.  The probability that one of us is doing 
64-bit builds under Windows is quite small.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/