Re: Problem setting buffer size for gfortran ( v 11.2)
Hi, On 24.02.22 08:57, Bertini, Denis Dr. via Fortran wrote: Additonnaly i ran interactively my test program without slurm on with just one MPI process on I think you either use Open MPI or MPICH. Can you try setting the environment variable when invoking MPI by adding the -x or -env (-envlist, ...) option like in: Open MPI mpirun -x GFORTRAN_UNFORMATTED_BUFFER_SIZE=1024000 ... cf. https://www.open-mpi.org/doc/v1.8/man1/mpirun.1.php or MPICH: mpiexec -env GFORTRAN_UNFORMATTED_BUFFER_SIZE 1024000 ... cf. https://www.mpich.org/static/docs/v3.1/www1/mpiexec.html See linked man pages for details and additional environment-related options. Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
Re: Problem setting buffer size for gfortran ( v 11.2)
Hi Tobias I can try that but on our cluster we are bound to use srun (slurm). Do you know how to use the same functionality with srun to set the environment variables. Best Denis From: Tobias Burnus Sent: Thursday, February 24, 2022 9:13:18 AM To: Bertini, Denis Dr.; Harald Anlauf Cc: fortran@gcc.gnu.org Subject: Re: Problem setting buffer size for gfortran ( v 11.2) Hi, On 24.02.22 08:57, Bertini, Denis Dr. via Fortran wrote: > Additonnaly i ran interactively my test program without slurm on with just > one MPI process on I think you either use Open MPI or MPICH. Can you try setting the environment variable when invoking MPI by adding the -x or -env (-envlist, ...) option like in: Open MPI mpirun -x GFORTRAN_UNFORMATTED_BUFFER_SIZE=1024000 ... cf. https://www.open-mpi.org/doc/v1.8/man1/mpirun.1.php or MPICH: mpiexec -env GFORTRAN_UNFORMATTED_BUFFER_SIZE 1024000 ... cf. https://www.mpich.org/static/docs/v3.1/www1/mpiexec.html See linked man pages for details and additional environment-related options. Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
Re: Problem setting buffer size for gfortran ( v 11.2)
Hi Denis, On 24.02.22 09:15, Bertini, Denis Dr. via Fortran wrote: I can try that but on our cluster we are bound to use srun (slurm). Do you know how to use the same functionality with srun to set the environment variables. I didn't – but the manual did: srun --export=... See: https://slurm.schedmd.com/srun.html#OPT_export_1 Good luck, Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
Re: [PATCH] PR fortran/84519 - [F2018] STOP and ERROR STOP statements with QUIET specifier
Le 23/02/2022 à 23:21, Harald Anlauf via Fortran a écrit : Dear Fortranners, Fortran 2018 added a QUIET= specifier to STOP and ERROR STOP statements. Janne already implemented the library side code four (4!) years ago, but so far the frontend implementation was missing. Furthermore, F2018 allows for non-default-integer stopcode expressions (finally!). The attached patch provides this implementation. That was not too much fun for the following reasons: - fixed format vs. free format - F95 and F2003 apparently did not require a blank between STOP and stopcode, while F2008+ do require it. This should explain for the three testcases. Regtested on x86_64-pc-linux-gnu. OK for mainline? One step closer to F2018! Please move the error from trans-stmt.cc to resolve.cc. Otherwise looks good, and you have a green light by Jerry, but I would rather defer this to gcc-13. Mikael
Re: [PATCH] PR fortran/84519 - [F2018] STOP and ERROR STOP statements with QUIET specifier
Dear Jerry, Mikael, thanks for the feedback! Am 24.02.22 um 12:50 schrieb Mikael Morin: Le 23/02/2022 à 23:21, Harald Anlauf via Fortran a écrit : Dear Fortranners, Fortran 2018 added a QUIET= specifier to STOP and ERROR STOP statements. Janne already implemented the library side code four (4!) years ago, but so far the frontend implementation was missing. Furthermore, F2018 allows for non-default-integer stopcode expressions (finally!). The attached patch provides this implementation. That was not too much fun for the following reasons: - fixed format vs. free format - F95 and F2003 apparently did not require a blank between STOP and stopcode, while F2008+ do require it. This should explain for the three testcases. Regtested on x86_64-pc-linux-gnu. OK for mainline? One step closer to F2018! Please move the error from trans-stmt.cc to resolve.cc. That is certainly cleaner. I've done this and rerun the regtest. As suggested by Jerry a simple run-time testcase with QUIET=.true. has been added. However, since I could not find a way to convince dejagnu that there should be no output, I simply check that the right values are passed to the runtime library. If somebody knows how to solve this and feels strongly about this, please proceed. Pushed as https://gcc.gnu.org/g:916b809fbfdd2740006270baf549bf22fe9ec3c4 Otherwise looks good, and you have a green light by Jerry, but I would rather defer this to gcc-13. Mikael Thanks, Harald
