LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
April 2006
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
Thread
2006.04.02 17:30 "Re: WORDS_BIGENDIAN makes libtiff platform dependent", by Bob Friesenhahn
> > > The use of WORDS_ENDIAN doesn't really improve > > > performance. > > > > If there is indeed a problem to be fixed (and I am not sure that there > > is), what solution do you propose to fix it. > > Why do we need such define's suddenly now? How was libtiff handling such > problems before? Earlier versions were using a define named 'HOST_BIGENDIAN' in libtiff/tiffconf.h: * HOST_BIGENDIAN native cpu byte order: 1 if big-endian (Motorola) * or 0 if little-endian (Intel); this may be used * in codecs to optimize code so it does not seem like there was a big change to me. Maybe this had already been figured out before in your build environment and you just did not realize it? Libtiff really does need to know the endian order, the size of 'short, 'int', 'long', bit order, etc., in order to work correctly for a given target. Bob ====================================== Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/