-
Notifications
You must be signed in to change notification settings - Fork 861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate bigcount interfaces for Fortran and C #12226
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't finished reading / understanding / reviewing both generate_bindings.py scripts yet, but since I'm so late for this and the clock is ticking on @jtronge's availability, I'm going to submit what I have so far.
|
||
lib@OMPI_LIBMPI_NAME@_usempif08_la_SOURCES = \ | ||
$(mpi_api_files) \ | ||
mpi-f08.F90 | ||
|
||
# These are generated; do not ship them | ||
nodist_lib@OMPI_LIBMPI_NAME@_usempif08_la_SOURCES = | ||
# nodist_lib@OMPI_LIBMPI_NAME@_usempif08_la_SOURCES = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go ahead and delete this line; don't just comment it out.
|
||
# JMS Somehow this variable substitution isn't quite working, and I | ||
# don't have time to figure it out. So just wholesale copy the file | ||
# list. :-( | ||
#pmpi_api_files = $(mpi_api_files:%=profile/p%) | ||
#pmpi_api_files = $(mpi_api_files:%=p%) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you can figure out why this substitution isn't working, go ahead and uncomment it. Otherwise, it would probably be ok to delete this whole commented-out block.
ompi/include/mpi.h.in
Outdated
@@ -1389,7 +1389,7 @@ OMPI_DECLSPEC extern struct ompi_predefined_datatype_t ompi_mpi_ub; | |||
/* | |||
* MPI API | |||
*/ | |||
|
|||
#ifndef OMPI_NO_MPI_PROTOTYPES |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only file in the whole tree where I see this macro used -- where does it come from?
If we're using it in our infrastructure, we prefer to always define boolean-like macros to be 0 or 1 (vs. defined or undefined). There's less of a chance for error that way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is left over from the standard ABI code; I can remove it for now.
IIRC the reason I didn't use a 0/1 macro there is because it would require adding the macro in mpicc or forcing the end user to add it. Both the standard ABI and the ompi ABI code were using mpi.h since some types defined there needed to be used in both versions, but the prototypes cannot be the same.
When we start working again on the standard ABI code, it might be better to refactor mpi.h out into multiple files to make this easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, gotcha -- those are good reasons. If you end up keeping something like this, having a comment to explain the deviation from our norm (i.e., using #ifndef
) would be good.
@@ -41,6 +41,36 @@ endif | |||
|
|||
headers = bindings.h | |||
|
|||
prototype_sources = \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably worth putting a comment before this line explaining what this macro is for -- it may not be intuitive to the casual code reader that these are all the files with bigcount APIs.
@@ -60,7 +90,7 @@ endif | |||
# List of all C files that have profile versions | |||
# |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might also be good to include in this comment before the interface_profile_sources
that the ompi_FOO.c
files have the ompi_
prefix because they were generated.
ompi/mpi/c/generate_bindings.py
Outdated
|
||
def main(): | ||
if len(sys.argv) < 2: | ||
# Fix required for Python 3.6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this comment mean -- does this mean that this script does not work if Python is < v3.6?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This a fix for Python v3.6, since the argparse
package has some limitations for that version. I have not tested this code below v3.6, unless the CI is using older versions.
ompi/mpi/c/generate_bindings.py
Outdated
sys.exit(1) | ||
|
||
parser = argparse.ArgumentParser(description='generate ABI header file and conversion code') | ||
subparsers = parser.add_subparsers() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused by this CLI interface. Running generate_bindings.py --help
shows this:
$ ./ompi/mpi/c/generate_bindings.py --help
usage: generate_bindings.py [-h] {header,source} ...
generate ABI header file and conversion code
positional arguments:
{header,source}
options:
-h, --help show this help message and exit
Which doesn't give me a lot of information about how to use this script. In ompi/mpi/c/Makefile.am
, I see it used like this:
$(PYTHON) $(srcdir)/generate_bindings.py source ompi $< > $@
I think that means it's falling down into the "source" sub-parser.
What's the header
sub-parser for? Is that for future functionality or something?
Would it be possible to use more traditional --foo=bar
kinds of CLI arguments, perchance?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can try to make --help
a little more descriptive about the sub-parsers. The source
sub-parser is designed to generate the source code from a template, in this case for the ompi ABI. The header
sub-parser is designed to auto-generate the prototype definitions, although it was only used previously for the standard ABI code (it could be useful for the ompi ABI as well).
The standard ABI functionality was completely removed from the Makefiles, but I've left the functionality in the script, that's why some of these arguments are still there but unused.
ompi/mpi/c/generate_bindings.py
Outdated
print('ERROR: missing subparser argument (see --help)') | ||
sys.exit(1) | ||
|
||
parser = argparse.ArgumentParser(description='generate ABI header file and conversion code') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this generating ABI files, or BigCount stuff? I thought this PR was about BigCount and ABI was future...?
...after reading a bunch more of generate_bindings.py
, I see that it looks like a lot of the ABI functionality is included, but it doesn't look like it's complete...? E.g., I don't see any other kind of ABI infrastructure (e.g., creating the other libraries, stacking the libraries and implementations like we talked about, etc.).
If we're too late in the game to fully dis-entangle ABI and bigcount into 2 wholly separate commits (with one almost certainly building upon the other), it would be good to explain that this commit has elements of stuff that will be used in an upcoming ABI commit and it wasn't separated because of lack of time blah blah blah. Otherwise, the reader (e.g., me) is left wondering why a "Bigcount" commit has a bunch of unused / half-done ABI stuff included.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I should have been more clear with my commit message. I removed all ABI-specific changes from the make-system, but the script still includes the unused ABI code. This seemed the best route to take, instead of completely removing the extra ABI code, which is not affecting how ompi is being built right now. I can remove it though.
ompi/mpi/c/generate_bindings.py
Outdated
args = parser.parse_args() | ||
|
||
# Always add the header | ||
print('/* THIS FILE WAS AUTOGENERATED BY ompi/mpi/c/abi.py. DO NOT EDIT BY HAND. */') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additionally, it might be better to have a traditional --outfile=FILENAME
kind of CLI arg that indicates the name of the file that you want to write to. This leaves stdout available for info/verbose/debug kinds of output.
ompi/mpi/c/generate_bindings.py
Outdated
* Functions requiring a bigcount implementation should have type COUNT in | ||
place of MPI_Count or int for each count parameter. Bigcount functions will | ||
be generated automatically for any function that includes a COUNT type. | ||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a larger comment here at the top explaining the purpose of this script, and at least a high-level overview of what it does / how it works. This is a very large script; having an intro to it at the top would be most helpful to the reader (e.g., me).
Should #12033 be closed (if this PR wholly replaces it)? |
config/ompi_setup_mpi_fortran.m4
Outdated
AS_IF([test $OMPI_TRY_FORTRAN_BINDINGS -ge $OMPI_FORTRAN_USEMPIF08_BINDINGS], | ||
[OMPI_FORTRAN_CHECK_TS([OMPI_FORTRAN_HAVE_TS=1])]) | ||
|
||
AC_SUBST(OMPI_MPI_SUBARRAYS_SUPPORTED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think lines 458 and 459 should b moved below line 472 since it is there that we may be setting OMPI_MPI_SUBARRAYS_SUPPORTED and OMPI_MPI_ASYNC_PROTECTS_NONBLOCKING to true.
docs/developers/bindings.rst
Outdated
The Fortran file ``api_f08_generated.F90`` contains all the internal subroutine | ||
definitions, each of which makes a call into corresponding C functions. Two | ||
different C files are generated: ``api_f08_ts_generated.c`` contains support | ||
for compilers with TS 29113 support, allowing the use of ``CFI_cdesc_t`` types; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be nice to add a hyperlink here, e.g. https://fortranwiki.org/fortran/show/Fortran+2018
/azp run |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
3 similar comments
Hello! The Git Commit Checker CI bot found a few problems with this PR: 01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
1 similar comment
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
4 similar comments
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
Hello! The Git Commit Checker CI bot found a few problems with this PR: 5127029: Add ELEMENT_COUNT for MPI_Get_elements_x
fc151a8: Add DATATYPE, STATUS, and GREQUEST_ types*
e673867: Add int, char, and MPI_Info-related types
01fa44e: Add PARTITIONED_COUNT type
Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks! |
0590dd1
to
c7c06e2
Compare
fa6f257
to
2811c1f
Compare
60ea322
to
ab496c4
Compare
bot:ompi:retest |
bot:ompi:retest |
odd the jenkins community CI is failing in an autogen.pl run:
|
bot:ompi:retest |
b86d7de
to
c3e5885
Compare
related to PR open-mpi#12226 don't pay much attention to the top level MPI_Buffer_detach etc. code as it will be redone in open-mpi#12226. Signed-off-by: Howard Pritchard <[email protected]>
This adds scripts for generating the C API bindings from template files, while also generating bigcount interfaces for those that require them. The binding script also include initial support for the mpi_f08 Fortran bindings, but doesn't yet make any changes to fortran/use-mpi-f08 Python >=3.6 is required for running these scripts, which is only necessary when the binding files have not already been generated. Users of the distribution tarball should not need to generate these files and thus should not require Python. Co-authored-by: mphinney1100 <[email protected]> Co-authored-by: Howard Pritchard <[email protected]> Signed-off-by: Jake Tronge <[email protected]>
@jsquyres its ready! |
This updates fortran/use-mpi-f08 to generate most of the Fortran bindings from a script and template files. It also adds support for Fortran TS 29113 when possible, allowing for better Fortran array handling that matches the standard. The C files were imported from PR open-mpi#10302 and converted to templates to be fed into the binding script. Co-authored-by: Gilles Gouaillardet <[email protected]> Co-authored-by: Howard Pritchard <[email protected]> Signed-off-by: Jake Tronge <[email protected]>
This adds scripts for generating the C and Fortran mpi_f08 API bindings from template files, while also generating bigcount interfaces for those that require them. On the Fortran side it also adds support for TS 29113 when possible, allowing for better Fortran array handling that matches the standard (some files were imported from PR #10302).
Python >=3.6 is required for running these scripts, which is only necessary when the binding files have not already been generated. Users of the distribution tarball should not need to generate these files and thus should not require Python.
We used https://github.com/cea-hpc/pcvs-benchmarks and the MPI4PY test suite to help ensure all big count interfaces (C and Fortran) are being generated.
PR #12033 is a previous version of this focused specifically on ABI support.