[petsc-users] PETSc with 64 bit integer

[Barry Smith]

On May 30, 2012, at 11:01 AM, Keita Teranishi wrote:

> Jed,
>  
> Thanks for the reply! How about the other third-party software? Does it convert PETScInt to “int”?

   For packages that support 64 bit integers (hypre, superlu_dist, ...) the --download-package option causes the 64 bit integer version to be built automatically.  The flag     self.requires32bitint = 0 in superlu_dist.py (for example) indicates if the package supports 64 bit int. If you build the external package yourself you need to make sure you build the 64 bit integer version.   PETSc assumes that external packages that use BLAS/LAPACK know what they are doing with regard to calling BLAS/LAPACK when using 64 bit integers.

   PETSc built with 64 bit integers does not use external packages that use 32 bit int (except BLAS/LAPACK), that is it does not convert the 64 bit int to 32 bit (except for BLAS/LAPACK). 

   Barry

>  
> Regards,
> Keita
>  
> From: petsc-users-bounces at mcs.anl.gov [mailto:petsc-users-bounces at mcs.anl.gov] On Behalf Of Jed Brown
> Sent: Wednesday, May 30, 2012 10:58 AM
> To: PETSc users list
> Subject: Re: [petsc-users] PETSc with 64 bit integer
>  
> On Wed, May 30, 2012 at 10:52 AM, Keita Teranishi <keita at cray.com> wrote:
> Hi,
>  
> Is there any requirement for BLAS/LAPACK to install PETSc with 64-bit integer option?
>  
> No, PETSc distinguishes between PetscInt and BLAS ints (PetscBLASInt in the source).
>  
>  
> Thanks,
> ====================================
> Keita Teranishi
> Scientific Library Group
> Cray Inc.
> keita at cray.com
> ======================================
>  
>