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.21 21:20 "Re: libtiff 4.0 compiler warning on x64 in tif_read.c", by Edward Lam

Olivier Paquet wrote:
> 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.

Changing those two read_ahead declarations to tmsize_t seems to appease 
VC8. If there's no objections, perhaps you can make the changes?

> 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.

That's too bad. I would have assumed most people are on 64-bit gcc these 
days.

Thanks,
-Edward