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
October 2009

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

2009.10.28 22:43 "Libtiff release soon, please advise", by Bob Friesenhahn
2009.10.29 02:27 "Re: Libtiff release soon, please advise", by Edward Lam
2009.10.29 02:58 "Re: Libtiff release soon, please advise", by Bob Friesenhahn
2009.10.29 03:54 "Re: Libtiff release soon, please advise", by Edward Lam
2009.10.29 15:22 "Re: Libtiff release soon, please advise", by Bob Friesenhahn
2009.10.30 01:22 "Re: Libtiff release soon, please advise", by Bob Friesenhahn
2009.10.30 13:51 "Re: Libtiff release soon, please advise", by Edward Lam

2009.10.29 02:27 "Re: Libtiff release soon, please advise", by Edward Lam

Bob Friesenhahn wrote:
> I plan to cut new libtiff releases soon.  While I don't intend to fix 
> all existing (or many) known bugs before those releases are cut (and 
> there are many bugs listed in libtiff bugzilla), this would be a good 
> time to remind of any dire issues known to exist which should 
> definitely be fixed before a libtiff release.

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

Basically, it is saying that we should be adding -fno-strict-aliasing to 
the gcc (3+?) compiler options when compiling with -O2. Probably none of 
libtiff was written with strict aliasing in mind? If so, it sounds like 
a good and easy thing to do for avoiding potential bad code generation.

Regards,
-Edward