[petsc-dev] Possible bugs when using TS with ViennaCL

[Jed Brown]

Karl Rupp <rupp at mcs.anl.gov> writes:
> I should have been more precise: If we configure PETSc to use OpenMP 
> through threadcomm, then we run into issues. OpenMP and OpenCL code  per 
> se, i.e. without any PETSc-code involved, is not causing troubles (and 
> is a common build with ViennaCL). If I configure
>   --with-openmp
> but without
>   --with-threadcomm --with-pthreadclasses
> then execution is fine. Conversely, configuring
>   --with-threadcomm --with-pthreadclasses
> but without
>   --with-openmp
> also works. If all three options are supplied, wrong results are 
> obtained. Weird. I'll keep it on my list, but will focus on other items 
> first.

Okay, your diagnosis sounds right.  Gotta reduce this eventually so we
can file bug reports.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140129/9d17139c/attachment.sig>