> On Feb 27, 2016, at 8:22 PM, Boyce Griffith wrote:
>
> Barry —
>
> I haven’t been following master, and so maybe these have already been
> addressed, but is there a chance that fixes for the performance issues Amneet
> found (options in setting up lots of KSPs in small-block ASM,
Thanks
> On Feb 28, 2016, at 8:55 PM, Jeff Hammond wrote:
>
>
>
> On Sunday, February 28, 2016, Satish Balay wrote:
> This build is using gnu compilers with MKL. And PETSc configure
> doesn't guess compiler shortcuts like -mlk [or -framework Veclib] type
> options..
>
> Sounds like a BS design by M
On Sunday, February 28, 2016, Satish Balay wrote:
> This build is using gnu compilers with MKL. And PETSc configure
> doesn't guess compiler shortcuts like -mlk [or -framework Veclib] type
> options..
Sounds like a BS design by Matt :-)
Jeff
>
> Satish
>
> On Sun, 28 Feb 2016, Jeff Hammond w
This build is using gnu compilers with MKL. And PETSc configure
doesn't guess compiler shortcuts like -mlk [or -framework Veclib] type
options..
Satish
On Sun, 28 Feb 2016, Jeff Hammond wrote:
> On Sunday, February 28, 2016, Matthew Knepley wrote:
>
> > On Sun, Feb 28, 2016 at 3:12 PM, Barry S
On Sunday, February 28, 2016, Matthew Knepley wrote:
> On Sun, Feb 28, 2016 at 3:12 PM, Barry Smith > wrote:
>
>>
>> Satish,
>>
>>Yeah, hypre totally botched its implementation of a way to check for
>> the blas/lapack libraries. I've iterated with them several times on the
>> basic problem
On Sun, Feb 28, 2016 at 3:12 PM, Barry Smith wrote:
>
> Satish,
>
>Yeah, hypre totally botched its implementation of a way to check for
> the blas/lapack libraries. I've iterated with them several times on the
> basic problem but they keep patching what they do, rather then discard all
> th
Satish,
Yeah, hypre totally botched its implementation of a way to check for the
blas/lapack libraries. I've iterated with them several times on the basic
problem but they keep patching what they do, rather then discard all their
incorrect code and handle it simply as they should.
Bar
Executing: cd
/pmi/cmpbib/compilation_BIB_gcc_redhat_petsc-master_debug/COMPILE_AUTO/petsc-master-debug/arch-linux2-c-debug/externalpackages/git.hypre/src
&& ./configure --prefix=/opt/petsc-master_debug MAKE=/bin/gmake
--libdir=/opt/petsc-master_debug/lib CC="/opt/openmpi-1.10.2/bin/mpicc"
CFLA
hypre folks,
One of our users was unable to build with your new hypre release candidate:
output below. It looks like your configure is still trying to check
--with-blas-lib= entries one at a time to find the blas routines. This won't
work because, for example, with MKL to use blas/lapack
Hi Barry,
the configuration of hypre looks broken since last night...?
Here is the log issued from our automatic compilation of
petsc-master.tar.gz at 2016-02-28 02h00:
http://www.giref.ulaval.ca/~cmpgiref/petsc-master-debug/configure_20160228_0200.log
Everything was fine until last night...
On Sunday, February 28, 2016, Karl Rupp wrote:
> Hi,
>
> I like the idea of having separate VECCUDA and VECVIENNACL, because it is
>> possible to implement VECCUDA without dependence on a C++ compiler (only
>> the CUDA compiler).
>>
>
> I don't understand this part. NVCC also requires a C++ host
> El 28 feb 2016, a las 10:45, Karl Rupp escribió:
>
> Hi,
>
>> I like the idea of having separate VECCUDA and VECVIENNACL, because it is
>> possible to implement VECCUDA without dependence on a C++ compiler (only the
>> CUDA compiler).
>
> I don't understand this part. NVCC also requires a
Hi,
I like the idea of having separate VECCUDA and VECVIENNACL, because it is
possible to implement VECCUDA without dependence on a C++ compiler (only the
CUDA compiler).
I don't understand this part. NVCC also requires a C++ host compiler and
is fairly picky about the supported compilers.
13 matches
Mail list logo
