Hi Andre, I used a clean build directory but don't recall if I reconfigured. I was 10 minutes away from leaving for the airport! I'll try again when I am back at base.
Please, everyone else, don't hesitate to review and test. Regards Paul On Tue, 24 Jun 2025, 23:47 Andre Vehreschild, <ve...@gmx.de> wrote: > Hi Paul, > > thanks for trying it. I can only affirm the need of whitespace fixes for > the > fifth patch. But that got me only a warning on a clean trunk. So > application > should be fine. Attached is an updated patch of part 5 of the patch series > with > all whitespace errors removed. Sorry for the bother. > > As to your compile error: Did you build in a clean directory? The patch > adds > another library and therefore makefiles are changed. This may need another > configure run. I can only imagine that something went wrong there and the > dependencies in the build system have not been updated, because that is > what > the error message indicates. Can you try again? > > Because "works for me" using a clean build directory. How can I help you > further? > > Regards, > Andre > > On Tue, 24 Jun 2025 17:23:31 +0100 > Paul Richard Thomas <paul.richard.tho...@gmail.com> wrote: > > > Hi Andre, > > > > All six patches require git apply --whitespace=fix --ignore-space-change > < > > ~/prs/Shared_Memory/pr88076_v1_x.patch to apply. > > > > The build fails with: > > Makefile:3848: caf/.deps/caf_error.Plo: No such file or directory > > make[2]: *** No rule to make target 'caf/.deps/caf_error.Plo'. Stop. > > make[2]: Leaving directory > > '/home/pault/gitsources/build/x86_64-pc-linux-gnu/libgfortran' > > make[1]: *** [Makefile:16529: install-target-libgfortran] Error 2 > > make[1]: Leaving directory '/home/pault/gitsources/build' > > make: *** [Makefile:2668: install] Error 2 > > > > I am afraid that I have timed out for the next two weeks - sorry. > > > > Regards > > > > Paul > > > > > > On Tue, 24 Jun 2025 at 14:10, Andre Vehreschild <ve...@gmx.de> wrote: > > > > > Hi all, > > > > > > this series of patches (six in total) adds a new coarray backend > library to > > > libgfortran. The library uses shared memory and processes to implement > > > running multiple images on the same node. The work is based on work > > > started by > > > Thomas and Nicolas Koenig. No changes to the gfortran compile part are > > > required > > > for this. > > > > > > Unfortunately I found some defects in the gfortran compiler, that > needed > > > to be > > > fixed. These are the first four tiny patches. The fifth patch then > adds the > > > library and sixth patches the testcases in > > > gcc/testsuite/gfortran.dg/coarray to > > > also run (and pass) when linked against caf_shmem. > > > > > > The development has been done on x86_64-pc-linux-gnu / Fedora 41. I am > > > curious > > > to learn which fixes will be needed for other platforms. > > > > > > This will be the last big patch that was funded by the STF/STA. My > funding > > > has > > > run out and I will only be available for a few days before a new > project > > > will > > > consume my attention. Therefore please bring any deficiencies to my > > > attention > > > as soon as possible. > > > > > > I have done some performance measurement against OpenCoarrays measuring > > > coarray_icarr from https://github.com/gutmann/coarray_icar . The > figures > > > are: > > > > > > OpenCoarrays (mpich4-backend): 165.578s (real 2m59,947s) > > > -------------------------------------------------- > > > caf_shmem (16-trunk): 61.489s (real 1m3,681s) > > > > > > The first number is the "Model run time:" as reported by the program. > In > > > the > > > parentheses the real run time as reported by the bash command `time` is > > > given. > > > > > > Both are done using a debug build of coarray_icar on an Intel Core > > > i7-5775C CPU > > > @ 3.30GHz having 24GB, and running Fedora Linux 41 with all recent > patches. > > > > > > Regards, > > > Andre > > > -- > > > Andre Vehreschild * Email: vehre ad gmx dot de > > > > > > -- > Andre Vehreschild * Email: vehre ad gmx dot de >
