outdated PaStiX

Bug #1127337 reported by Jan Blechta
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Dorsal
Fix Committed
Undecided
Johannes Ring

Bug Description

Since dolfin rev 7434 the PaStiX newer than release 3725 should be probably pulled by dorsal. With 3725 dolfin can't be built with message:

...../dolfin/la/PaStiXLUSolver.cpp:173:35: error: âAPI_THREAD_FUNNELEDâ was not declared in this scope

Related branches

Johannes Ring (johannr)
Changed in dorsal:
status: New → Fix Committed
assignee: nobody → Johannes Ring (johannr)
Revision history for this message
Jan Blechta (blechta) wrote :

Shouldn't also some check of pastix version should be introduced to dolfin configure system in order to user gets a more informative message than
...../dolfin/la/PaStiXLUSolver.cpp:173:35: error: âAPI_THREAD_FUNNELEDâ was not declared in this scope

Revision history for this message
Garth Wells (garth-wells) wrote : Re: [Bug 1127337] Re: outdated PaStiX

PaStiX should not be enabled by Dorsal. The installation is
complicated and depends on details of the available MPI
implementation.

Garth

On 18 February 2013 16:57, Jan Blechta <email address hidden> wrote:
> Shouldn't also some check of pastix version should be introduced to dolfin configure system in order to user gets a more informative message than
> ...../dolfin/la/PaStiXLUSolver.cpp:173:35: error: âAPI_THREAD_FUNNELEDâ was not declared in this scope
>
> --
> You received this bug notification because you are a member of Dorsal
> Core Team, which is subscribed to Dorsal.
> https://bugs.launchpad.net/bugs/1127337
>
> Title:
> outdated PaStiX
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dorsal/+bug/1127337/+subscriptions

Revision history for this message
Johannes Ring (johannr) wrote :

@Jan: Yes, there should be a version check for PaStiX.

@Garth: PaStiX is not enabled by default, except when using the {precise,quantal}-hpc.platform.

Revision history for this message
Jan Blechta (blechta) wrote :

BTW: what is compiling dolfin with pastix for if you have petsc without pastix?

Revision history for this message
Garth Wells (garth-wells) wrote :

On 19 February 2013 19:55, Jan Blechta <email address hidden> wrote:
> BTW: what is compiling dolfin with pastix for if you have petsc without
> pastix?
>

PaStiX + PETSc was badly broken and PETSc does not expose PaStiX
parameters that are very important for performance.

Garth

> --
> You received this bug notification because you are a member of Dorsal
> Core Team, which is subscribed to Dorsal.
> https://bugs.launchpad.net/bugs/1127337
>
> Title:
> outdated PaStiX
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dorsal/+bug/1127337/+subscriptions

Revision history for this message
Jan Blechta (blechta) wrote :

> > BTW: what is compiling dolfin with pastix for if you have petsc
> > without pastix?
> >
>
> PaStiX + PETSc was badly broken and PETSc does not expose PaStiX
> parameters that are very important for performance.
>

But I guess there is no way to use PaStiX if you have PETSc
compiled without PaStix, is it?

Revision history for this message
Garth Wells (garth-wells) wrote :

On 19 February 2013 20:21, Jan Blechta <email address hidden> wrote:
>> > BTW: what is compiling dolfin with pastix for if you have petsc
>> > without pastix?
>> >
>>
>> PaStiX + PETSc was badly broken and PETSc does not expose PaStiX
>> parameters that are very important for performance.
>>
>
> But I guess there is no way to use PaStiX if you have PETSc
> compiled without PaStix, is it?
>

It is perfectly possible to use PaStiX without PETSc installed.

Garth

> --
> You received this bug notification because you are a member of Dorsal
> Core Team, which is subscribed to Dorsal.
> https://bugs.launchpad.net/bugs/1127337
>
> Title:
> outdated PaStiX
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dorsal/+bug/1127337/+subscriptions

Revision history for this message
Jan Blechta (blechta) wrote :

 >> > BTW: what is compiling dolfin with pastix for if you have petsc
> >> > without pastix?
> >> >
> >>
> >> PaStiX + PETSc was badly broken and PETSc does not expose PaStiX
> >> parameters that are very important for performance.
> >>
> >
> > But I guess there is no way to use PaStiX if you have PETSc
> > compiled without PaStix, is it?
> >
>
> It is perfectly possible to use PaStiX without PETSc installed.
>
> Garth
>

Sorry for hijacking the bug report. But I'm a little bit confused so I
have few questions:

1. It seems that PaStiX can be used without PETSc directly by class
   PaStiXLUSolver in which case STLMatrix must be used. Am I right?
   Then it is odd (or bug?) that list_foo_solver_bar() list nothing for
   STL backend.

2. In this case is thread support available?

3. Only way to use PaStiX with MPI is through PETSc, right?

4. What is a primary way? Is PETSc/PaStiX solver tuned in dolfin?

Thanks

Jan

Revision history for this message
Johannes Ring (johannr) wrote :

After updating PaStiX to the 4030 release, DOLFIN can no longer detect it and I'm seeing the following error in CMakeError.log:

/usr/lib/ccache/gcc -DPASTIX_TEST_RUNS -fopenmp -I/home/johannr/dev/fenics/src/dorsal/trunk/Work/FEniCS/include -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -o CMakeFiles/cmTryCompileExec2542955030.dir/src.c.o -c /home/johannr/dev/fenics/src/dolfin/trunk/build2/CMakeFiles/CMakeTmp/src.c
In file included from /home/johannr/dev/fenics/src/dolfin/trunk/build2/CMakeFiles/CMakeTmp/src.c:7:0:
/home/johannr/dev/fenics/src/dorsal/trunk/Work/FEniCS/include/pastix.h:4:1: error: unknown type name ‘u_int64_t’

Any idea? What PaStiX release is known to work with DOLFIN?

Revision history for this message
Garth Wells (garth-wells) wrote :

On 20 February 2013 07:33, Johannes Ring <email address hidden> wrote:
> After updating PaStiX to the 4030 release, DOLFIN can no longer detect
> it and I'm seeing the following error in CMakeError.log:
>
> /usr/lib/ccache/gcc -DPASTIX_TEST_RUNS -fopenmp -I/home/johannr/dev/fenics/src/dorsal/trunk/Work/FEniCS/include -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -o CMakeFiles/cmTryCompileExec2542955030.dir/src.c.o -c /home/johannr/dev/fenics/src/dolfin/trunk/build2/CMakeFiles/CMakeTmp/src.c
> In file included from /home/johannr/dev/fenics/src/dolfin/trunk/build2/CMakeFiles/CMakeTmp/src.c:7:0:
> /home/johannr/dev/fenics/src/dorsal/trunk/Work/FEniCS/include/pastix.h:4:1: error: unknown type name ‘u_int64_t’
>
> Any idea? What PaStiX release is known to work with DOLFIN?
>

It's a PaStiX bug and it has been reported to the developers.

u_int64_t is not a standard C type. Just open pastix.h and change it
to uint64_t at the top of the file.

Garth

> --
> You received this bug notification because you are a member of Dorsal
> Core Team, which is subscribed to Dorsal.
> https://bugs.launchpad.net/bugs/1127337
>
> Title:
> outdated PaStiX
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dorsal/+bug/1127337/+subscriptions

Revision history for this message
Johannes Ring (johannr) wrote :

Thanks, that fixed the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.