AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.04.28 02:38 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 04:32 "Re: VC++ Release build causes problems", by Roy Darrall
2000.04.28 06:16 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 06:25 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 09:19 "VC++ Release build causes problems", by John Aldridge
2000.04.28 17:49 "Re: VC++ Release build causes problems", by Daniel McCoy
2000.04.29 00:27 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 17:27 "VC++ Release build causes problems", by Peter Montgomery
2000.04.28 18:33 "Re: VC++ Release build causes problems", by Jan Nijtmans
2000.04.28 20:39 "Re: VC++ Release build causes problems", by Daniel McCoy

2000.04.28 09:19 "VC++ Release build causes problems", by John Aldridge

Me again. I just loaded the strike image in The Gimp and saved it as an LZW compressed image and a non-compressed image. The non-compressed image works PERFECTLY under both debug and release builds. The LZW compressed image screws up royally under the release build but works fine in debug.

There was a thread on something very like this a year or so ago. The conclusion then was that libtiff is assuming that

   int x = somthing; // assume 32 bit int
   y = x << 32;      // or any greater shift

would always yield zero. However neither the C nor the C++ standard guarantee this behaviour, and compilers are entitled not to implement it.

--
Cheers,
John