David Wootton

I have been researching this with the intent of implementing a check for gfortran and XL Fortran, I have discovered the following: - There is a directive that can be...

@jjhursey asked me to check mpirun options to make sure that reasonable help text was displayed for each option and that the mpirun command recognized each option in running a...

I'm not expecting parameters like ppr to have individual help text since they are parameters to mpirun options such as --map-by or --bind-to which have their own help text.

I tested the remaining mpirun options, and have results in two files. I updated help.txt with more comments, flagged with '%%' to distinguish them from the first set, flagged with...

I looked at the list of symbols generated by @markalle testcase and tagged them in 3 categories, - >> static: Appear to be referenced in only one .c file and...

In my first pass thru the 3rdparty components, i got the number of symbols that need to be fixed for the following components - treematch: 158 - openpmix: 3 -...

Part 1 of solving this, making symbols in opal and ompi subdirectories static is solved by pull request #10825

The changes in the two open pull requests associated with this issue, #10859 and #10863 resolve the remaining incorrect symbols other than the following symbols in the 3rd-party/romio341 component. [error]...

Once pull requests #10825 #10859 and #10863 were merged into the main branch, the test case output listing improperly named external symbols is ``` Checking for bad symbol names: ***...

@awlauria This is the v5.0.x output after all pull requests were merged Checking for bad symbol names: *** checking /u/dwootton/ompi/lib/libmpi.so.80 [error] ad_get_env_vars [error] file_stats [error] romio_onesided_always_rmw [error] romio_onesided_inform_rmw [error] romio_onesided_no_rmw...