[petsc-dev] CMake-assisted CUDA builds ready

Jed Brown jedbrown at mcs.anl.gov
Wed Mar 20 15:33:34 CDT 2013

On Wed, Mar 20, 2013 at 3:19 PM, Karl Rupp <rupp at mcs.anl.gov> wrote:

> Yes, I know that this is a heavy operation. On the other hand, it only
> occurs after a reconfigure, so it's not supposed to happen too often.
> Anyway, with CUDA enabled I can deterministically reproduce the error in
> `next`:
>  >gt; rm -rf PETSC_ARCH/CMake*
>  >gt; PETSC_ARCH/conf/reconfigure-**xxx.py     # Fine, generates CMake
> build
>  >gt; PETSC_ARCH/conf/reconfigure-**xxx.py     # Fine, generates CMake
> build
>  >gt; make ... all                           # compiles
>  >gt; PETSC_ARCH/conf/reconfigure-**xxx.py     # Hangs, legacy fallback
> However, the problem does not show up without CUDA.

It would be friendly to track down the actual problem and report it as a
bug for them to save in their tracker and close when there has been no
action for years (and why is an infinite loop a problem anyway). ;-)

I guess I would add this CUDA work-around to cmakeboot.py.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130320/0c17b273/attachment.html>

More information about the petsc-dev mailing list