If this moves forward, I’d like to offer example code to target in Fiats (
https://go.lbl.gov/fiats). I presented automatic parallelization results
produced by compiling with LLVM flang-new for inference at the PAW-ATM
workshop at SC24 (see https://go.lbl.gov/just-write-fortran). It would be
great
Jerry,
See
https://github.com/BerkeleyLab/fiats/blob/c256784fbd3eb28053daad657fc01c3caaf562d4/src/fiats/neural_network_s.F90#L871.
The F2023_LOCALITY macro switches on the use of reduce locality. The
F2018_LOCALITY macro uses only locality specifiers that were in Fortran
2018. The F2008_LOCALITY
Hello world,
the attached patch makes sure that procedures from abstract
interfaces and dummy arguments are not put into the global
symbol table, and are not checked against global symbols.
Regression-tested. OK for trunk?
Best regards
Thomas
Abstract interfaces and dummy arguments ar
Hi Steve and Jerry,
thanks for the review and the proposed changes. I have based on them, but
needed to adapt some places, because the meaning was changed. Can you please
take another look?
Jerry, where do I find this check-script? In bin/ nothing jumps out at me to be
a check-script.
Thanks,
Dear Chenlu,
Thank you for your interest!
I have forwarded your e-mail to the gfortran mailing list, where
discussion of gfortran takes place.
Best regards
Thomas
Weitergeleitete Nachricht
Betreff: [GSoC][Fortran – DO CONCURRENT] Interest in 2025 GSoC – Fortran
DO
Hi Thomas,
Am 10.03.25 um 21:01 schrieb Thomas Koenig:
Hello world,
the attached patch makes sure that procedures from abstract
interfaces and dummy arguments are not put into the global
symbol table, and are not checked against global symbols.
Regression-tested. OK for trunk?
Best regards
Dear all,
here's a patch that fixes a 15-regression (NULL pointer dereference)
and implements a missed check of SAVE of a COMMON in a BLOCK construct.
Two separate testcases, as the respective error messages occur at
different stages in the frontend.
Regtested on x86_64-pc-linux-gnu. OK for ma
