Message Passing Interface: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Alter: title, chapter. | Use this bot. Report bugs. | Suggested by Corvus florensis | #UCB_webform 1746/2500
Markstock (talk | contribs)
m HP spun off HPE and bought Cray, so HPE now makes cray-mpich; disclosure: I work at HPE
Line 162:
* [[Open MPI]] (not to be confused with [[OpenMP]]) was formed by the merging FT-MPI, LA-MPI, [[LAM/MPI]], and PACX-MPI, and is found in many [[TOP-500]] [[supercomputer]]s.
 
Many other efforts are derivatives of MPICH, LAM, and other works, including, but not limited to, commercial implementations from [[Hewlett-PackardHewlett_Packard_Enterprise|HPHPE]], [[Intel]], [[Microsoft]], and [[NEC]].
 
While the specifications mandate a C and Fortran interface, the language used to implement MPI is not constrained to match the language or languages it seeks to support at runtime. Most implementations combine C, C++ and assembly language, and target C, C++, and Fortran programmers. Bindings are available for many other languages, including Perl, Python, R, Ruby, Java, and [[Control Language|CL]] (see [[#Language bindings]]).