piplib thread-safe?

[Uday K Bondhugula]

I'm using piplib-1.4.0 (on Linux 64-bit). Is piplib meant to be
thread-safe? While using piplib from multi-threaded code, I run into
race conditions and crashes. Besides segfaults, messages I get before
things crash include:

Aie !!! Flag 4 inattendu.

Syserr : traiter : tableau too small

Aie !!! Flag 7 inattendu.

Integer overflow

Calling code was compiled with gcc -O3 -fopenmp.

Thanks,
-Uday

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

[Sven Verdoolaege]

On Tue, Feb 28, 2012 at 01:02:43PM +0530, Uday K Bondhugula wrote:
>
> I'm using piplib-1.4.0 (on Linux 64-bit). Is piplib meant to be
> thread-safe?

No.

skimo

[Uday K Bondhugula]

Is it easy to make it thread-safe?

Thanks,
-Uday

>
> skimo

[Sven Verdoolaege]

On Tue, Feb 28, 2012 at 02:09:18PM +0530, Uday K Bondhugula wrote:
> On 02/28/2012 01:07 PM, Sven Verdoolaege wrote:
> >On Tue, Feb 28, 2012 at 01:02:43PM +0530, Uday K Bondhugula wrote:
> >>I'm using piplib-1.4.0 (on Linux 64-bit). Is piplib meant to be
> >>thread-safe?
> >
> >No.
>
> Is it easy to make it thread-safe?

No idea.
Personally, I would think it would be easier to use isl instead...
YMMV

skimo

[Uday K Bondhugula]

Yes, it does vary. I already have it with ISL and PIP (controlled by an
option - contributed by Tobias Grosser). Multithreading while using isl
(8 threads) is already slower than single-threaded with PIP for my
application.

with PIP: 0.89s
with ISL (1 thread): 1.75s
with ISL (8 threads): 1.28s