Problem with GCC 13.3.0 / mpich 4.1

ogus (it should print F). If I comment out anything related with MPI the code works fine; it also works fine with mpich/4.1 compiled with other GCC versions (12.X, 13.1, 13.2, 14.1) What would you suggest for further investigation/reporting? Thanks Salvatore Filippone module const_mod int

Re: Problem with GCC 13.3.0 / mpich 4.1

ttings(save1,info) write(0,*) 'Done first clone settings' return end subroutine check_save_smoothers end program tsm ------ On Mon, Jul 1, 2024 at 4:12 PM Salvatore Filippone < filippone.salvat...@gm

Re: Problem with GCC 13.3.0 / mpich 4.1

Sorry for the noise, when compiled with OpenMPI/4.1.4 the problem does not appear. So, it looks like it's an MPICH bug rather than a GCC one. On Mon, Jul 1, 2024 at 4:14 PM Salvatore Filippone < filippone.salvat...@gmail.com> wrote: > Ooops, looks like the attachment was not we

FINAL subroutines

Hi all The attached code compiles and runs fine under both GNU and Intel, but it produces different results, in particular the FINAL subroutine is invoked just once with GNU, three times with Intel. It seems to me that they cannot both be right; I am not sure what the standard is mandating in this

Re: FINAL subroutines

te(*,*) 'Calling new_outer_type ' call new_outer_type(wrapper,i) write(*,*) 'DeAllocating wrapper ' deallocate(wrapper) end program testfinal On Mon, Jan 24, 2022 at 2:50 PM Salvatore Filippone < filippone.salvat...@gmail.com> wrote: > Hi all > The attached

Re: FINAL subroutines

; memory). > > Your code compiled with gfortran (with Paul's patches in place) shows no > errors or leaks from valgrind. > > So, in summary, in this case I think the current gfortran is missing some > finalizations (which are fixed by Paul's patches), and ifort is likely >

Re: FINAL subroutines

Is there any reason these patches can not be applied and use this test >> as a test case? >> >> Regards, >> >> Jerry >> >> On 1/24/22 8:11 AM, Salvatore Filippone via Fortran wrote: >> > Thanks a lot >> > (yes, I suspected both gfortran and

Re: FINAL subroutines

onstructors and one or two other corner cases. Following that, the > existing finalization calls will be brought into the framework as the new > calls. > > Best regards > > Paul > > > On Thu, 27 Jan 2022 at 07:17, Salvatore Filippone < > filippone.salvat...@gmail.co

Error message

Dear all I am getting the following error message, which I find quite confusing 68 | use amg_prec_mod | 1 Fatal Error: Mismatch in components of derived type '__vtype_psb_c_par_mat_mod_Psb_c_par_mat_type' from 'psb_c_par_mat_mod' at (1): expecting 'bldext', but got 'aclsum' compil

Re: Error message

s that first > module. It seems like there are then multiple definitions of the derived > type > (from different modules) that are out of sync. So, recompiling everything > resolves this issue for me. > > But, as I said, I'm not 100% sure that this is the explanation! > >