| AWARE [SYSTEMS] | Imaging expertise for the Delphi developer | |||||||
![]() |
TIFF and LibTiff Mailing List Archive | |||||||
LibTiff Mailing List
TIFF and LibTiff Mailing List Archive Contact
The TIFF Mailing List Homepage |
Thread2009.10.30 13:51 "Re: Libtiff release soon, please advise", by Edward LamBob Friesenhahn wrote: > I added -Wstrict-aliasing=2 to the libtiff build options and I see that > many more warnings are produced. I am not sure how afraid we should be > of these warnings since the software has continued to work. Yes, it's probably fine. The gcc manual says that -Wstrict-aliasing=2 can give false positives. FWIW, I just tried compiling CVS HEAD with gcc 4.3.3 and compiler options "-g -O2 -Wall -Wstrict-aliasing=2" and there were no aliasing warnings. I did get some 64-bit warnings in tif_unix.c though. Looks like gcc 4.4 has changed warning behaviour in this regard? I should also note that for Visual Studio 2005, there's no such thing as a strict pointer aliasing compiler option. I think we're compiling libtiff on Windows assuming pointer aliasing. To bring up a side issue since you're willing to look at warnings. Bug 2068 is a one line fix. :) Cheers, -Edward |
|||||||