Karl Rupp <[email protected]> writes:

> For the sake of completeness of this thread:
>
> Mani's build included
> --with-threadcomm --with-pthreadclasses --with-openmp
> which seems the be the cause of the problem. Without these flags,  the 
> problem disappears and results are correct. If I remember correctly, 
> this is a more fundamental problem in threadcomm rather than specific to 
> the ViennaCL bindings, yet we clearly need to fix it.

[repost from petsc-maint]

Evidently threads are a liability right now.  Do you know what caused
this behavior so we can avoid it in the future?

Attachment: pgpNMdZIIo8UO.pgp
Description: PGP signature

Reply via email to