Re: [OMPI devel] v2.0.0rc4 is released
Hi Jeff, sorry for a very short report. I saw the warning below at the end of installation of openmpi-2.0.0rc4. Is this okay? $ make install ... make install-exec-hook make[3]: Entering directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' WARNING! Common symbols found: show_help_lex.o: 0004 C opal_show_help_yyleng show_help_lex.o: 0008 C opal_show_help_yytext hostfile_lex.o: 0004 C orte_util_hostfile_leng hostfile_lex.o: 0008 C orte_util_hostfile_text rmaps_rank_file_lex.o: 0004 C orte_rmaps_rank_file_leng rmaps_rank_file_lex.o: 0008 C orte_rmaps_rank_file_text make[3]: [install-exec-hook] Error 1 (ignored) make[3]: Leaving directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' make[1]: Leaving directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' Regards, Tetsuya Mishima 2016/07/07 2:40:25、"devel"さんは「[OMPI devel] v2.0.0rc4 is released」で書 きました > While crossing our fingers and doing mystical rain dances, we're hoping that 2.0.0rc4 is the last rc before v2.0.0 (final) is released. Please test! > > https://www.open-mpi.org/software/ompi/v2.x/ > > Changes since rc3 (the list may look long, but most are quite small corner cases): > > - Lots of threading fixes > - More fixes for the new memory patcher system > - Updates to NEWS and README > - Fixed some hcoll bugs > - Updates for external PMIx support > - PMIx direct launching fixes > - libudev fixes > - compatibility fixes with ibv_exp_* > - 32 bit compatibility fixes > - fix some powerpc issues > - various OMPIO / libnbc fixes from Lisandro Dalcin > - fix some Solaris configury patching > - fix PSM/PSM2 active state detection > - disable PSM/PSM2 signal hijacking by default > - datatype fixes > - portals4 fixes > - change ofi MTL to only use a limited set of OFI providers by default > - fix OSHMEM init error check > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: http://www.open-mpi.org/community/lists/devel/2016/07/19153.php
Re: [OMPI devel] v2.0.0rc4 is released
This is a warning that can be safely ignored. That being said, this can be seen as a false positive (unless we fix flex or its generated output). Also, and generally speaking, these kind of warnings is for developers only (e.g. end users can do nothing about that). That raises the question : what could/should we do ? - master filters out these false positives, should we backport this to v2.x ? - should we simply not check for common symbols when building from a tarball ? Cheers, Gilles On 7/7/2016 2:03 PM, tmish...@jcity.maeda.co.jp wrote: Hi Jeff, sorry for a very short report. I saw the warning below at the end of installation of openmpi-2.0.0rc4. Is this okay? $ make install ... make install-exec-hook make[3]: Entering directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' WARNING! Common symbols found: show_help_lex.o: 0004 C opal_show_help_yyleng show_help_lex.o: 0008 C opal_show_help_yytext hostfile_lex.o: 0004 C orte_util_hostfile_leng hostfile_lex.o: 0008 C orte_util_hostfile_text rmaps_rank_file_lex.o: 0004 C orte_rmaps_rank_file_leng rmaps_rank_file_lex.o: 0008 C orte_rmaps_rank_file_text make[3]: [install-exec-hook] Error 1 (ignored) make[3]: Leaving directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' make[1]: Leaving directory `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' Regards, Tetsuya Mishima 2016/07/07 2:40:25、"devel"さんは「[OMPI devel] v2.0.0rc4 is released」で書 きました While crossing our fingers and doing mystical rain dances, we're hoping that 2.0.0rc4 is the last rc before v2.0.0 (final) is released. Please test! https://www.open-mpi.org/software/ompi/v2.x/ Changes since rc3 (the list may look long, but most are quite small corner cases): - Lots of threading fixes - More fixes for the new memory patcher system - Updates to NEWS and README - Fixed some hcoll bugs - Updates for external PMIx support - PMIx direct launching fixes - libudev fixes - compatibility fixes with ibv_exp_* - 32 bit compatibility fixes - fix some powerpc issues - various OMPIO / libnbc fixes from Lisandro Dalcin - fix some Solaris configury patching - fix PSM/PSM2 active state detection - disable PSM/PSM2 signal hijacking by default - datatype fixes - portals4 fixes - change ofi MTL to only use a limited set of OFI providers by default - fix OSHMEM init error check -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ ___ devel mailing list de...@open-mpi.org Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel Link to this post: http://www.open-mpi.org/community/lists/devel/2016/07/19153.php ___ devel mailing list de...@open-mpi.org Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel Link to this post: http://www.open-mpi.org/community/lists/devel/2016/07/19158.php
Re: [OMPI devel] v2.0.0rc4 is released
Hi Gilles san, thank you for your quick comment. I fully understand the meaning of the warning. Regarding the question you raise, I'm afraid that I'm not sure which solution is better ... Regards, Tetsuya Mishima 2016/07/07 14:13:02、"devel"さんは「Re: [OMPI devel] v2.0.0rc4 is released」で書きました > This is a warning that can be safely ignored. > > > That being said, this can be seen as a false positive (unless we fix > flex or its generated output). > > Also, and generally speaking, these kind of warnings is for developers > only (e.g. end users can do nothing about that). > > > That raises the question : what could/should we do ? > > - master filters out these false positives, should we backport this to > v2.x ? > > - should we simply not check for common symbols when building from a > tarball ? > > > Cheers, > > > Gilles > > On 7/7/2016 2:03 PM, tmish...@jcity.maeda.co.jp wrote: > > Hi Jeff, sorry for a very short report. I saw the warning below > > at the end of installation of openmpi-2.0.0rc4. Is this okay? > > > > $ make install > > ... > > make install-exec-hook > > make[3]: Entering directory > > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > > WARNING! Common symbols found: > >show_help_lex.o: 0004 C opal_show_help_yyleng > >show_help_lex.o: 0008 C opal_show_help_yytext > > hostfile_lex.o: 0004 C orte_util_hostfile_leng > > hostfile_lex.o: 0008 C orte_util_hostfile_text > > rmaps_rank_file_lex.o: 0004 C orte_rmaps_rank_file_leng > > rmaps_rank_file_lex.o: 0008 C orte_rmaps_rank_file_text > > make[3]: [install-exec-hook] Error 1 (ignored) > > make[3]: Leaving directory > > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > > make[2]: Nothing to be done for `install-data-am'. > > make[2]: Leaving directory > > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > > make[1]: Leaving directory > > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > > > > Regards, > > Tetsuya Mishima > > > > 2016/07/07 2:40:25、"devel"さんは「[OMPI devel] v2.0.0rc4 is released」で書 > > きました > >> While crossing our fingers and doing mystical rain dances, we're hoping > > that 2.0.0rc4 is the last rc before v2.0.0 (final) is released. Please > > test! > >> https://www.open-mpi.org/software/ompi/v2.x/ > >> > >> Changes since rc3 (the list may look long, but most are quite small > > corner cases): > >> - Lots of threading fixes > >> - More fixes for the new memory patcher system > >> - Updates to NEWS and README > >> - Fixed some hcoll bugs > >> - Updates for external PMIx support > >> - PMIx direct launching fixes > >> - libudev fixes > >> - compatibility fixes with ibv_exp_* > >> - 32 bit compatibility fixes > >> - fix some powerpc issues > >> - various OMPIO / libnbc fixes from Lisandro Dalcin > >> - fix some Solaris configury patching > >> - fix PSM/PSM2 active state detection > >> - disable PSM/PSM2 signal hijacking by default > >> - datatype fixes > >> - portals4 fixes > >> - change ofi MTL to only use a limited set of OFI providers by default > >> - fix OSHMEM init error check > >> > >> -- > >> Jeff Squyres > >> jsquy...@cisco.com > >> For corporate legal information go to: > > http://www.cisco.com/web/about/doing_business/legal/cri/ > >> ___ > >> devel mailing list > >> de...@open-mpi.org > >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > >> Link to this post: > > http://www.open-mpi.org/community/lists/devel/2016/07/19153.php > > ___ > > devel mailing list > > de...@open-mpi.org > > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > > Link to this post: http://www.open-mpi.org/community/lists/devel/2016/07/19158.php > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/develLink to this post: http://www.open-mpi.org/community/lists/devel/2016/07/19159.php
[OMPI devel] Caught ibv_create_ah error in executing multi-node MPI program with openmpi-1.10.3
Hi guys, I have a problem regarding the subject. The detail is below. Is there anybody who can answer this behavior is a restriction of openmpi or something? I executed an mpi program and caught the following error related to ibv_create_ah. [sho@host0 ~]$ /opt/openmpi1103_debug/bin/mpirun -host host0,host1 -npernode 1 -np 2 ./sample PROC(0): senddata = 10 libibverbs: ibv_create_ah failed to query port. [host1:4395] *** An error occurred in MPI_Send [host1:4395] *** reported by process [139776618004481,0] [host1:4395] *** on communicator MPI_COMM_WORLD [host1:4395] *** MPI_ERR_OTHER: known error not in list [host1:4395] *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, [host1:4395] ***and potentially your MPI job) host0 has a ConnectX-3 HCA with 2 ports and a cable is connected with the port 2. host1 has a ConnectX-4 HCA with 1 port and a cable is connected with the port 1. The function udcm_endpoint_init_data seems to pass a remote port number to ibv_create_ah. I added a printf to output remote_msg->mm_port_num and found it output 1 on host0, output 2 on host1. Is this correct? I think a local port number should be specified to ibv_create_ah. static int udcm_endpoint_init_data (mca_btl_base_endpoint_t *lcl_ep) : : ah_attr.dlid = lcl_ep->rem_info.rem_lid; ah_attr.port_num = remote_msg->mm_port_num; <** It's a remote port. ah_attr.sl= mca_btl_openib_component.ib_service_level; ah_attr.src_path_bits = lcl_ep->endpoint_btl->src_path_bits; udep->ah = ibv_create_ah (lcl_ep->endpoint_btl->device->ib_pd, &ah_attr); I modified the above code to specify a local port directly. The sample code was executed correctly on host0 and host1. With best regards, Takashi Sato
Re: [OMPI devel] v2.0.0rc4 is released
It looks like we forgot to move https://github.com/open-mpi/ompi/commit/62c45e4a to v2.x (i.e., the functionality that only displays the common symbols warning if you have a .git directory). > On Jul 7, 2016, at 1:03 AM, tmish...@jcity.maeda.co.jp wrote: > > Hi Jeff, sorry for a very short report. I saw the warning below > at the end of installation of openmpi-2.0.0rc4. Is this okay? > > $ make install > ... > make install-exec-hook > make[3]: Entering directory > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > WARNING! Common symbols found: > show_help_lex.o: 0004 C opal_show_help_yyleng > show_help_lex.o: 0008 C opal_show_help_yytext > hostfile_lex.o: 0004 C orte_util_hostfile_leng > hostfile_lex.o: 0008 C orte_util_hostfile_text >rmaps_rank_file_lex.o: 0004 C orte_rmaps_rank_file_leng >rmaps_rank_file_lex.o: 0008 C orte_rmaps_rank_file_text > make[3]: [install-exec-hook] Error 1 (ignored) > make[3]: Leaving directory > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > make[2]: Nothing to be done for `install-data-am'. > make[2]: Leaving directory > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > make[1]: Leaving directory > `/home/mishima/mis/openmpi/openmpi-pgi16.5/openmpi-2.0.0rc4' > > Regards, > Tetsuya Mishima > > 2016/07/07 2:40:25、"devel"さんは「[OMPI devel] v2.0.0rc4 is released」で書 > きました >> While crossing our fingers and doing mystical rain dances, we're hoping > that 2.0.0rc4 is the last rc before v2.0.0 (final) is released. Please > test! >> >> https://www.open-mpi.org/software/ompi/v2.x/ >> >> Changes since rc3 (the list may look long, but most are quite small > corner cases): >> >> - Lots of threading fixes >> - More fixes for the new memory patcher system >> - Updates to NEWS and README >> - Fixed some hcoll bugs >> - Updates for external PMIx support >> - PMIx direct launching fixes >> - libudev fixes >> - compatibility fixes with ibv_exp_* >> - 32 bit compatibility fixes >> - fix some powerpc issues >> - various OMPIO / libnbc fixes from Lisandro Dalcin >> - fix some Solaris configury patching >> - fix PSM/PSM2 active state detection >> - disable PSM/PSM2 signal hijacking by default >> - datatype fixes >> - portals4 fixes >> - change ofi MTL to only use a limited set of OFI providers by default >> - fix OSHMEM init error check >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> ___ >> devel mailing list >> de...@open-mpi.org >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19153.php > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19158.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [OMPI devel] [2.0.0rc4] dlopen_test crash with xlc
Paul, What was the configure string you used for this? We have a Jenkins CI mechanism for XL, but it is using XLC 13.1.3 on that system and we haven't been runing 'make check'. I have another system that has XLC 13.1.2 that I can test on as well. I'm not sure if I'll be able to fix without Nathan's help, but I can at least try to reproduce. Thanks, Josh On Wed, Jul 6, 2016 at 4:58 PM, Paul Hargrove wrote: > The issue reported in > https://www.open-mpi.org/community/lists/devel/2016/06/19107.php is still > present on both my little-endian Power8 and big-endian Power7 systems. > I know Nathan had been working on this, but I've lost track of the issue > and/or pr number(s). > > -Paul > > -- > Paul H. Hargrove phhargr...@lbl.gov > Computer Languages & Systems Software (CLaSS) Group > Computer Science Department Tel: +1-510-495-2352 > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19156.php >
Re: [OMPI devel] [2.0.0rc4] dlopen_test crash with xlc
Josh, Big-endian Power7: $ xlc -qversion IBM XL C/C++ for Linux, V13.1 Version: 13.01.. $ export OBJECT_MODE=64 $ [...]/configure -prefix=[] --enable-debug \ CC=xlc CFLAGS="-q64" --with-wrapper-cflags="-q64" \ CXX=xlC CXXFLAGS="-q64" --with-wrapper-cxxflags="-q64" \ FC=xlf FCFLAGS="-q64" --with-wrapper-fcflags="-q64" \ --disable-oshmem-fortran --with-hwloc=$HOME/hwloc-1.11.3 Note the --with-hwloc is there because this is the xlc version that was crashing building the embedded hwloc. Am retesting now without that flag, but don't expect it has any relation to the SEGV in the patcher code. Little-endian Power8: $ xlc -qversion IBM XL C/C++ for Linux, V13.1.2 (5725-C73, 5765-J08) Version: 13.01.0002. $ [...]/configure -prefix=[] --enable-debug \ CC=xlc CXX=xlC FC=xlf --disable-mpi-fortran There is no xlf installation on this system. -Paul On Thu, Jul 7, 2016 at 8:39 AM, Josh Hursey wrote: > Paul, > > What was the configure string you used for this? > > We have a Jenkins CI mechanism for XL, but it is using XLC 13.1.3 on that > system and we haven't been runing 'make check'. I have another system that > has XLC 13.1.2 that I can test on as well. I'm not sure if I'll be able to > fix without Nathan's help, but I can at least try to reproduce. > > Thanks, > Josh > > > On Wed, Jul 6, 2016 at 4:58 PM, Paul Hargrove wrote: > >> The issue reported in >> https://www.open-mpi.org/community/lists/devel/2016/06/19107.php is >> still present on both my little-endian Power8 and big-endian Power7 systems. >> I know Nathan had been working on this, but I've lost track of the issue >> and/or pr number(s). >> >> -Paul >> >> -- >> Paul H. Hargrove phhargr...@lbl.gov >> Computer Languages & Systems Software (CLaSS) Group >> Computer Science Department Tel: +1-510-495-2352 >> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 >> >> ___ >> devel mailing list >> de...@open-mpi.org >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2016/07/19156.php >> > > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19163.php > -- Paul H. Hargrove phhargr...@lbl.gov Computer Languages & Systems Software (CLaSS) Group Computer Science Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
[OMPI devel] Class information in OpenMPI
Hi all, I want to know if there is “class diagram” for OpenMPI code base that shows existing classes and dependencies/associations. Are there any available tools to extract and visualize this information. — Murali
Re: [OMPI devel] [2.0.0rc4] dlopen_test crash with xlc
I don't think a ticket or PR was filed for this. I was able to reproduce on a Power8 machine, and filed the issue below: https://github.com/open-mpi/ompi/issues/1854 Nathan I added you to the ticket since it sounded like you had an idea where the problem was. On Thu, Jul 7, 2016 at 12:48 PM, Paul Hargrove wrote: > Josh, > > Big-endian Power7: > > $ xlc -qversion > IBM XL C/C++ for Linux, V13.1 > Version: 13.01.. > > $ export OBJECT_MODE=64 > > $ [...]/configure -prefix=[] --enable-debug \ >CC=xlc CFLAGS="-q64" --with-wrapper-cflags="-q64" \ >CXX=xlC CXXFLAGS="-q64" --with-wrapper-cxxflags="-q64" \ >FC=xlf FCFLAGS="-q64" --with-wrapper-fcflags="-q64" \ > --disable-oshmem-fortran --with-hwloc=$HOME/hwloc-1.11.3 > > > Note the --with-hwloc is there because this is the xlc version that was > crashing building the embedded hwloc. > Am retesting now without that flag, but don't expect it has any relation > to the SEGV in the patcher code. > > Little-endian Power8: > > $ xlc -qversion > IBM XL C/C++ for Linux, V13.1.2 (5725-C73, 5765-J08) > Version: 13.01.0002. > > $ [...]/configure -prefix=[] --enable-debug \ >CC=xlc CXX=xlC FC=xlf --disable-mpi-fortran > > > There is no xlf installation on this system. > > -Paul > > > On Thu, Jul 7, 2016 at 8:39 AM, Josh Hursey wrote: > >> Paul, >> >> What was the configure string you used for this? >> >> We have a Jenkins CI mechanism for XL, but it is using XLC 13.1.3 on that >> system and we haven't been runing 'make check'. I have another system that >> has XLC 13.1.2 that I can test on as well. I'm not sure if I'll be able to >> fix without Nathan's help, but I can at least try to reproduce. >> >> Thanks, >> Josh >> >> >> On Wed, Jul 6, 2016 at 4:58 PM, Paul Hargrove wrote: >> >>> The issue reported in >>> https://www.open-mpi.org/community/lists/devel/2016/06/19107.php is >>> still present on both my little-endian Power8 and big-endian Power7 systems. >>> I know Nathan had been working on this, but I've lost track of the issue >>> and/or pr number(s). >>> >>> -Paul >>> >>> -- >>> Paul H. Hargrove phhargr...@lbl.gov >>> Computer Languages & Systems Software (CLaSS) Group >>> Computer Science Department Tel: +1-510-495-2352 >>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 >>> >>> ___ >>> devel mailing list >>> de...@open-mpi.org >>> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >>> Link to this post: >>> http://www.open-mpi.org/community/lists/devel/2016/07/19156.php >>> >> >> >> ___ >> devel mailing list >> de...@open-mpi.org >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2016/07/19163.php >> > > > > -- > Paul H. Hargrove phhargr...@lbl.gov > Computer Languages & Systems Software (CLaSS) Group > Computer Science Department Tel: +1-510-495-2352 > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > > ___ > devel mailing list > de...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2016/07/19164.php >
Re: [OMPI devel] [OMPI users] Class information in OpenMPI
We used to have Doxygen support that would create what you are asking for, but I don’t think anyone has maintained it in a long time. I ran “doxygen” at the top-level directory and it did indeed generate a bunch of html, but I’m not sure it is all that helpful. You might take a look and see if it helps enough to be useful. Could be that someone will contribute updated Doxygen support to make it better… > On Jul 7, 2016, at 11:57 AM, Emani, Murali wrote: > > Hi all, > > I want to know if there is “class diagram” for OpenMPI code base that shows > existing classes and dependencies/associations. Are there any available tools > to extract and visualize this information. > > > — > Murali > > ___ > users mailing list > us...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/07/29594.php
Re: [OMPI devel] Class information in OpenMPI
FWIW, I have my private notes on process and datatype -related structs. https://rivis.github.io/doc/openmpi/openmpi-source-reading.en.xhtml They are created by my hands with the help of Autodia. http://www.aarontrevena.co.uk/opensource/autodia/ > I want to know if there is “class diagram” for OpenMPI code base that shows > existing classes and dependencies/associations. Are there any available tools > to extract and visualize this information. Thanks, KAWASHIMA Takahiro
