Message-ID: 12921.953244709@sss.pgh.pa.us
To: "Ivo" <ivo.penzar@infolink-software.com>
Subject: Re: -D_REENTRANT for libtiff and jpeg?
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 16 Mar 2000 17:11:49 -0500
cc: tiff@olympiakos.com
Comments: In-reply-to "Ivo" <ivo.penzar@infolink-software.com>message dated "Thu, 16 Mar 2000 14:20:11 +0100"
In-reply-to: <003301bf8f4a$62f860e0$5101a8c0@STORMTROOPER>
References: <38CFCC1B.B75FE060@med-web.com> <38CFD836.2B9@srz-berlin.de> <003301bf8f4a$62f860e0$5101a8c0@STORMTROOPER>
Sender: owner-tiff@olympiakos.com


"Ivo" <ivo.penzar@infolink-software.com> writes:
> So far, so good (almost). Nevertheless, I am still not complitely sure if
> there could be some non-reentrant functions or static variables deep into
> the libtiff or jpeg libraries?

libjpeg is thread-safe as long as (a) you don't have multiple threads
operating concurrently on the same jpeg object, and (b) your underlying
C library (particularly malloc/free) is thread-safe.  You can have
multiple jpeg objects being manipulated concurrently by different
threads.

ISTR that libtiff used to have static variables, but that was years ago;
perhaps it's been cleaned up?

                        regards, tom lane
                        organizer, Independent JPEG Group

