Hi everybody,
I have recently being trying to run SLEPc on GPUs, but I am experiencing some
trouble.
I think I correctly installed PETSc to run on GPUs, as I can actually see an
execution time difference in PETSc programs when run with or without -vec_type
cusp -mat_type aijcusp.
When I try to
> El 24/7/2015, a las 10:09, Leoni, Massimiliano
> escribió:
>
> Hi everybody,
>
> I have recently being trying to run SLEPc on GPUs, but I am experiencing some
> trouble.
> I think I correctly installed PETSc to run on GPUs, as I can actually see an
> execution time difference in PETSc pro
Hi all,
I came across this [alleged] bug when installing petsc with GPU support: if I
run configure with option -with-cusp-include=... it complains I should also set
-with-cusp-lib, but cusp is a pure template library, so there is no static or
shared library to link against.
As an alternative,
> -Original Message-
> From: Jose E. Roman [mailto:jro...@dsic.upv.es]
> Sent: 24 July 2015 09:20
> To: Leoni, Massimiliano
> Cc: petsc-dev@mcs.anl.gov; Alejandro Lamas
> Subject: Re: [petsc-dev] [SLEPc - GPU] Problems running SLEPc on GPUs
>
> As you can seen in section 8.3 of SLEPc’s use
Hi Massimiliano,
> I came across this [alleged] bug when installing petsc with GPU support:
if I run configure with option –with-cusp-include=… it complains I
should also set –with-cusp-lib, but cusp is a pure template library, so
there is no static or shared library to link against.
Correct.
> On Jul 24, 2015, at 9:28 AM, Karl Rupp wrote:
>
> Hi Massimiliano,
>
> > I came across this [alleged] bug when installing petsc with GPU support:
>> if I run configure with option –with-cusp-include=… it complains I
>> should also set –with-cusp-lib, but cusp is a pure template library, so
>>
I have fixed the following:
When configure options like --with-cusp-include=xxx are given and no
corresponding --with-cusp-lib=yyy is needed
configure will no longer print an inaccurate error message that you must also
set a --with-cusp-lib=yyy but instead
correctly use the provided value
> On Jul 19, 2015, at 2:25 PM, Jared Crean wrote:
>
>Hello,
>Yeah, Clang.jl was supposed to be the answer to that, but it doesn't
> handle preprocessor macros and a few other things quite right.
>
>Anyways, type detection is working, but when running the tests with
> Petsc
