Hi Jerry,
for the moment only the static library is configured in the build scripts.
Therefore only that is build named libcaf_shmem.a That's completely correct
and desired.
I have asked the same question about performance or stress tests and got
only the coarray_icar (link in the 0/6 mail). So when you find something
suitable, please throw it at caf_shmem.
Regards,
Andre
Andre Vehreschild * ve...@gmx.de
Am 26. Juni 2025 19:15:06 schrieb Jerry D <jvdelis...@gmail.com>:
On 6/26/25 12:22 AM, Andre Vehreschild wrote:
Hi Jerry,
thanks for testing. I have fixed IMO most of the whitespace issues in the
patch attached to this mail:
https://gcc.gnu.org/pipermail/fortran/2025-June/062349.html
About the 32 vs. 64 bit versions of the libraries: I never got in touch with
that. I am doing the same as for caf_single. In fact I copied the Makefile.am
portion of caf_single and changed it to generate caf_shmem. Do you get both
versions for caf_single? Did you try a clean rebuild? Can anyone give me a
pointer on what I do wrong here?
Regards,
Andre
--- snip ---
I was able to apply the patches without any issues. I did see some
trailing white space in a few places.
In running the testsuite the test lock_1.f90 test fails, unable to link
to the new library.
Hi all, I have seen oddities before. I started all over. My build
script always completely erases the previous build directory.
Regardless, after a fresh build, I am unable to reproduce the lock_1.f90
failure.
Regarding where the libraries get installed, I was expecting to see the
various libcaf_shmem libraries along side the libgfortran libraries. If
someone would clarify that I would appreciate it.
I think the next step is to do some hard testing. I was thinking about
the Opencoarrays Burgers test. Any other suggestions?
Andre, do you have any hard performance tests to suggest? Some sort of
stress test?
Jerry
