Re: [petsc-dev] patch for wrong integer type

2019-02-04 Thread Karl Rupp via petsc-dev
Hi Fabian, I just merged the patch to master and maint. Please let us know whether this solves the issue. Best regards, Karli On 2/4/19 8:51 PM, Matthew Knepley via petsc-dev wrote: On Mon, Feb 4, 2019 at 2:42 PM Fabian.Jakub via petsc-dev mailto:petsc-dev@mcs.anl.gov>> wrote: Dear Pe

Re: [petsc-dev] cray warning - reduction in alignment ignored

2019-02-04 Thread Smith, Barry F. via petsc-dev
Hmm, I looked at the docs and the aligned just specifies a minimum alignment (the compile could possibly use a larger alignment) So I am not sure why we even use it; but I do know that the code did not work "somewhere" without that attribute. Presumably the warning message is somewhat "s

[petsc-dev] patch for wrong integer type

2019-02-04 Thread Fabian.Jakub via petsc-dev
Dear Petsc Team, I recently had segfaults when dumping DMPlexs through the PetscObjectViewer into hdf5 files This happens to me with 64 bit integers and I think there is a PetscInt where an int should be placed. Please have a look at the attached patch. Yours, Fabian From 78a8c48ed0956277273d5

Re: [petsc-dev] cray warning - reduction in alignment ignored

2019-02-04 Thread Hapla Vaclav via petsc-dev
Barry, I realized the problem appeared because of --with-precision=single. Without that the warnings disappeared. Maybe DMNetwork code should be completely disabled for single (all tests actually require double)? Or is it expected to work fine with single on other archs? I also wanted to run th