On 3/12/19 8:49 PM, Balay, Satish wrote:
1. You might want to check 'Feature-request: Must use GNU compilers
with CUDA' thread on petsc-maint.
Yes, I see this thread now. Thanks.
2. what does nvcc use internally on summit?
It defaults to the GCC suite but it is supposed to also support the
Jed, yes, I'm on petsc-maint and I see this thread now. Thanks; I'll take a
look. (I've had a crazy day and have been more behind than usual on email.)
--Richard
On 3/12/19 8:48 PM, Jed Brown wrote:
Richard, are you not on petsc-maint? There was a thread about this today.
PGI "community editi
MPI_Type_create_resized (if needed).
"Balay, Satish via petsc-dev" writes:
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2019/03/01/make_master_arch-linux-pkgs-64idx_thrash.log
> has the following [but for some reason - its filtered out from the warning
> count]
>
> In file in
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2019/03/01/make_master_arch-linux-pkgs-64idx_thrash.log
has the following [but for some reason - its filtered out from the warning
count]
>>>
In file included from
/sandbox/petsc/petsc.master-3/src/dm/impls/forest/p4est/dmp4est.c:13:0:
/sa
1. You might want to check 'Feature-request: Must use GNU compilers
with CUDA' thread on petsc-maint.
2. what does nvcc use internally on summit?
3. On linux - nvcc defaults to using g++ internally (as far as I know)
- so we added that check. But you might want to remove that check - if
things wo
Richard, are you not on petsc-maint? There was a thread about this today.
PGI "community edition" is free now. We could add it to our test suite.
https://www.pgroup.com/products/community.htm
"Smith, Barry F. via petsc-dev" writes:
> Richard,
>
> You need to remove the isGNU() test a
Richard,
You need to remove the isGNU() test and then experiment with getting the
Nvidia tools to use the compiler you want it to use.
No one has made a serious effort to use any other compilers but Gnu (at
least not publicly).
Barry
> On Mar 12, 2019, at 10:40 PM, Mills, Ri
Fellow PETSc developers,
If I try to configure PETSc with CUDA support on the ORNL Summit system using
non-GNU compilers, I run into an error due to the following code in
packages/cuda.py:
def configureTypes(self):
import config.setCompilers
if not config.setCompilers.Configure.isGNU(
Got it. Thanks.
--Junchao Zhang
On Tue, Mar 12, 2019 at 2:01 PM Smith, Barry F.
mailto:bsm...@mcs.anl.gov>> wrote:
It is because you have manual page documentation for it. The comment above
it starts with /*@ if you don't want a manual page then remove the @ if you
want a manual page bu
It is because you have manual page documentation for it. The comment above
it starts with /*@ if you don't want a manual page then remove the @ if you
want a manual page but no stub then use /*@C
Barry
> On Mar 12, 2019, at 1:46 PM, Zhang, Junchao via petsc-dev
> wrote:
>
> I declar
> On 12 Mar 2019, at 18:46, Zhang, Junchao via petsc-dev
> wrote:
>
> How to fix that? I do not think I need a Fortran stub for that. I found under
> ftn-auto, not all .c functions have a Fotran counterpart. What is the rule?
Comment block starts with /*@C I think
It's in the dev manual un
I declared PETSC_INTERN PetscErrorCode VecLockWriteSet_Private(Vec,PetscBool)
in vecimp.h and defined it in src/vec/vec/interface/rvector.c. I used
PETSC_INTERN and _Private since currently the function is only used in the Vec
packaged and is not public. I met this compilation warning
src/vec/
BTW: you could just try out the changes from jed/python3-futurize -
and see if that is sufficient for the fedora build of petsc-3.10
[when we tested that branch - it worked for our common use cases]
Satish
On Tue, 12 Mar 2019, Balay, Satish via petsc-dev wrote:
> petsc-3.11 - likely to be relea
petsc-3.11 - likely to be released by the end of the month, will work with
python3
Wrt PETSc-3.10 the feature is in branch jed/python3-futurize (which is
off 3.10 - so it can be cleanly merged to 3.10) - but then - some
fixes were added later (so will have to identify them and back-port - not
sur
No, Python-3 support is in 'master'.
Antonio Trande via petsc-dev writes:
> Hi all.
>
> Does exist a patch for compiling PETSc-3.10.4 with Python3?
>
> --
> ---
> Antonio Trande
> Fedora Project
> mailto 'sagitter at fedoraproject dot org'
> GPG key: 0x6e0331dd1699e4d7
> GPG key server: https:/
On 11 Mar 2019, at 23:59, Jed Brown via petsc-dev
mailto:petsc-dev@mcs.anl.gov>> wrote:
One could imagine PETSc written so that all Mat operations like
transpose and products return lazy representations, with a method that
makes it explicit. Would eliminate all the Transpose variants in the
ma
16 matches
Mail list logo
