ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
a01884a6a0
openmpi/.gitignore

676 строки
19 KiB
Plaintext
Исходник Обычный вид История

Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
.libs
.deps
.libs
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
.dirstamp
.DS_Store
.cdt*
.project
.gdb*
Reworked Mellanox OpenMPI CI with Azure Pipelines. Signed-off-by: Artem Ryabov <artemry@mellanox.com>
2020-01-14 20:20:51 +03:00
.idea
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
.hgrc
.hgignore
.hg
.hgignore_local
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.la
*.lo
*.o
*.so
*.a
Add *.dwarf to the ignores as Mac Yosemite now generates these files
2014-11-18 19:47:20 +03:00
*.dwarf
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.dSYM
*.S
*.loT
*.orig
*.rej
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
*.bak
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.class
*.xcscheme
Ignore *.out files generated by making tarballs
2014-11-19 23:31:07 +03:00
*.out
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*.plist
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
*.orig
*.obj
*.mod
*.i90
*.ii
*.ti
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
*.exe
*.log
*.trs
Add support for Singularity containers, including a .m4 file for checking if Singularity is available and an orte/schizo component for setting the proper support if a container was given as the executable Cleanup the configury so we properly check for Singularity under the various typical use-cases Bring the Singularity support online. We have to turn "off" the sm BTL as it segfaults from inside the container - root cause remains unclear. Also turned "off" the various OPAL shmem components in case they are involved and someone else tries to use them. Happily, the vader BTL works just fine!
2016-02-11 10:43:13 +03:00
*.sapp
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
*~
gitignore: a few more consolidations
2014-12-20 04:55:29 +03:00
*\\#
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
Makefile
Makefile.in
static-components.h
*\\#
config.cache
aclocal.m4
autom4te.cache
config.log
config.status
configure
libtool
doxygen
bin
lib
cscope.*
etags
GRTAGS
GSYMS
GTAGS
GPATH
vc70.pdb
.hgrc
.hgignore
.hg
.hgignore_local
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
stamp-h?
dist: Autogenerate AUTHORS file Per discussion at the Summer 2017 developers meeting, generate the AUTHORS list at make dist time, rather than trying to keep it up to date and merge on the branches by hand. While most of the data is generated from git, the organization list was maintained by hand. The general feeling at the meeting was that the organization list was not adding value and there were concrete cases where it involved much chasing by the RMs, so it has been removed. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
2017-07-19 20:14:24 +03:00
AUTHORS
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
ar-lib
ylwrap
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
config.lt
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
config.guess
config.sub
depcomp
compile
install-sh
ltmain.sh
missing
mkinstalldirs
libtool.m4
lt~obsolete.m4
ltdl.m4
argz.m4
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
ltargz.m4
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
ltsugar.m4
ltversion.m4
ltoptions.m4
Introduce the MCA framework system. This formalizes the interface frameworks must provide. Other changes: - Added a flag to the MCA variable system to indicate a variable should go away when its group does. Both mca_base_framework_var_register() and mca_base_component_var_register() set this flag. Notes: - mca_base_components_open is deprecated. It will be removed in a future commit. - All frameworks should use MCA_BASE_FRAMEWORK_DECLARE to declare their framework structure. - All calls to framework open/close functions should be changed to use the mca_base_framework_* functions. - Instead of special-casing installdirs a flag was added to prevent calling into the variable system when opening a framework. - Ralph: Clarify the functional definition of the "register" function in the MCA framework object - it had the same name as another function that does a totally different thing. - As per discussion with Ralph the behavior of mca_base_framework_register() is to always call mca_base_framework_components_register() if the framework's register function was successful. This removed the need for frameworks to have to call this function directly. This commit was SVN r28237.
2013-03-28 01:10:18 +04:00
config/project_list.m4
config/autogen_found_items.m4
config/opal_get_version.sh
config/test-driver
gitignore: trim a lot of kruft This gitignore was simply the catenation of all the svn:ignore properties. However, .gitignore is pretty good at regular expressions that span the entire tree, so we can consolidate/remove a lot of redundant entries.
2014-12-20 04:33:51 +03:00
config/mca_no_configure_components.m4
config/mca_m4_config_include.m4
config/ext_no_configure_components.m4
config/ext_m4_config_include.m4
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
contrib/build-mca-comps-outside-of-tree/btl_tcp2_config.h
contrib/build-mca-comps-outside-of-tree/btl_tcp2_config.h.in
contrib/build-mca-comps-outside-of-tree/config
contrib/build-mca-comps-outside-of-tree/aclocal.m4
contrib/dist/linux/compile_debian_mlnx_example
contrib/dist/mofed/compile_debian_mlnx_example
contrib/dist/mofed/debian/changelog
contrib/dist/mofed/debian/control
contrib/dist/mofed/debian/copyright
contrib/dist/mofed/debian/rules
contrib/platform/intel/bend/*orcm*
contrib/scaling/orte_no_op
contrib/scaling/mpi_no_op
contrib/scaling/mpi_barrier
Remove stale global variables Revamp the event notification integration to rely on the PMIx event chaining and remove the duplicate chaining in OPAL. This ensures we get system-level events that target non-default handlers. Restore the hostname entries for MPI-level error messages, but provide an MCA param (orte_hostname_cutoff) to remove them for large clusters where the memory footprint is problematic. Set the default at 1000 nodes in the job (not the allocation). Begin first cut at memory profiler Some minor cleanups of memprobe Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2016-12-31 18:37:24 +03:00
contrib/scaling/mpi_memprobe
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
examples/hello_c
examples/hello_cxx
examples/hello_mpifh
examples/hello_usempi
examples/hello_usempif08
examples/ring_c
examples/ring_cxx
examples/ring_mpifh
examples/ring_usempi
examples/ring_usempif08
examples/connectivity_c
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
examples/ring_oshmem
examples/hello_oshmem
examples/ring_oshmemfh
examples/hello_oshmemfh
git: Ignore OSHMEM C++ wrapper artifacts Signed-off-by: Brian Barrett <bbarrett@amazon.com>
2017-09-08 18:03:27 +03:00
examples/hello_oshmemcxx
Update git/hg ignore files This commit was SVN r31875.
2014-05-22 09:00:26 +04:00
examples/oshmem_circular_shift
examples/oshmem_max_reduction
examples/oshmem_shmalloc
examples/oshmem_strided_puts
examples/oshmem_symmetric_data
Ignore spc_example Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-06-17 02:28:44 +03:00
examples/spc_example
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/debuggers/*.in
ompi/debuggers/dlopen_test
ompi/debuggers/predefined_gap_test
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
ompi/debuggers/predefined_pad_test
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/mpi.h
ompi/include/mpif-config.h
ompi/include/mpif.h
fortran: fix f08 bindings only define the unique fortran symbol depending on - CAPS - PLAIN - SINGLE_UNDERSCORE - DOUBLE_UNDERSCORE and bind the f08 symbol to the uniquely defined C symbol. Use real data structures to make the code simpler. (perl script written by Jeff)
2015-07-24 03:51:21 +03:00
ompi/include/mpif-c-constants-decl.h
ompi/include/mpif-c-constants.h
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/mpif-common.h
ompi/include/mpi-ext.h
ompi/include/mpif-ext.h
fortran: fix f08 bindings only define the unique fortran symbol depending on - CAPS - PLAIN - SINGLE_UNDERSCORE - DOUBLE_UNDERSCORE and bind the f08 symbol to the uniquely defined C symbol. Use real data structures to make the code simpler. (perl script written by Jeff)
2015-07-24 03:51:21 +03:00
ompi/include/mpif-f08-types.h
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/mpif-handles.h
ompi/include/mpif-io-constants.h
ompi/include/mpif-constants.h
ompi/include/mpif-io-handles.h
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/include/mpif-sizeof.h
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
ompi/include/mpi_portable_platform.h
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/include/ompi/version.h
ompi/include/ompi/frameworks.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mca/coll/basic/coll-basic-version.h*
ompi/mca/coll/demo/config
ompi/mca/coll/demo/coll_demo_config.h*
ompi/mca/coll/demo/coll-demo-version.h*
ompi/mca/coll/ml/coll_ml_lex.c
ompi/mca/coll/self/coll-self-version.h*
ompi/mca/coll/sm/coll-sm-version.h*
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mca/crcp/ompi_crcp.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
io/romio321: update .gitignore and remove two files that should have never been commited Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2018-06-26 04:51:35 +03:00
ompi/mca/io/romio321/romio/adio/include/romioconf.h
ompi/mca/io/romio321/romio/include/mpio.h
ompi/mca/io/romio321/romio/localdefs
ompi/mca/io/romio321/romio/test/fcoll_test.f
ompi/mca/io/romio321/romio/test/fmisc.f
ompi/mca/io/romio321/romio/test/fperf.f
ompi/mca/io/romio321/romio/test/large_file.c
ompi/mca/io/romio321/romio/test/misc.c
ompi/mca/io/romio321/romio/test/pfcoll_test.f
ompi/mca/io/romio321/romio/test/runtests
ompi/mca/io/romio321/romio/util/romioinstall
Silence coverity warnings, remove/ignore build product Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-06-25 17:05:11 +03:00
ompi/mca/io/romio321/romio/test/syshints.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Ignore generated file Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-02-13 18:30:00 +03:00
ompi/mca/osc/monitoring/osc_monitoring_template_gen.h
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mca/pml/v/autogen.vprotocols
ompi/mca/pml/v/mca_vprotocol_config_output
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/mca/rte/orte/ompi-ps.1
ompi/mca/rte/orte/ompi-clean.1
ompi/mca/rte/orte/mpiexec.1
ompi/mca/rte/orte/ompi-top.1
ompi/mca/rte/orte/ompi-server.1
Update .gitignore This commit was SVN r31024.
2014-03-12 17:20:50 +04:00
ompi/mca/rte/orte/ompi-restart.1
ompi/mca/rte/orte/ompi-checkpoint.1
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/mca/rte/orte/mpirun.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update gitignore per the latest values of svn:ignore This commit was SVN r29238.
2013-09-25 00:41:45 +04:00
ompi/mca/sharedfp/addproc/mca_sharedfp_addproc_control
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Ignore generated file Signed-off-by: Ralph Castain <rhc@pmix.org>
2019-02-07 04:17:34 +03:00
ompi/mca/topo/treematch/config.h
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/c/profile/p*.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/configure-fortran-output.h
ompi/mpi/fortran/mpiext/mpi-ext-module.F90
ompi/mpi/fortran/mpiext/mpi-f08-ext-module.F90
Update .gitignore for Fortran MPI extensions files Signed-off-by: KAWASHIMA Takahiro <t-kawashima@jp.fujitsu.com>
2018-06-11 13:59:13 +03:00
ompi/mpi/fortran/mpiext-use-mpi/mpi-ext-module.F90
ompi/mpi/fortran/mpiext-use-mpi-f08/mpi-f08-ext-module.F90
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/mpif-h/sizeof_f.f90
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/mpif-h/profile/p*.c
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/mpif-h/profile/psizeof_f.f90
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
fortran/use-mpi-f08: revamp constant declarations In order to work around an issue with flang based compilers, avoid declaring bind(C) constants and use plain Fortran parameter instead. For example, type(MPI_Comm), bind(C, name="ompi_f08_mpi_comm_world") OMPI_PROTECTED :: MPI_COMM_WORLD is changed to type(MPI_Comm), parameter :: MPI_COMM_WORLD = MPI_Comm(OMPI_MPI_COMM_WORLD) Note that in order to preserve ABI compatibility, ompi/mpi/fortran/use-mpi-f08/constants.{c,h} have been kept even if its symbols are no more referenced by Open MPI. Refs. open-mpi/ompi#7091 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2019-10-24 05:05:29 +03:00
ompi/mpi/fortran/use-mpi-f08/mod/mpi-f08-constants.h
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/use-mpi-f08/sizeof_f08.f90
ompi/mpi/fortran/use-mpi-f08/sizeof_f08.h
ompi/mpi/fortran/use-mpi-f08/profile/psizeof_f08.f90
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-interfaces.h
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-file-interfaces.h
Update git/hg ignore files This commit was SVN r32768.
2014-09-20 09:00:28 +04:00
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-sizeof.f90
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-sizeof.h
Ignore new generated file Signed-off-by: Ralph Castain <rhc@open-mpi.org> (cherry picked from commit 19d5e5ad57a1e724ed02c6cbb0b5cdf4aff2fac7)
2018-06-02 02:35:07 +03:00
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-removed-interfaces.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/fortran/use-mpi-tkr/fortran_kinds.sh
ompi/mpi/fortran/use-mpi-tkr/fortran_sizes.h
ompi/mpi/fortran/use-mpi-tkr/mpi_kinds.ompi_module
fortran/use-mpi-tkr: update .gitignore ignore automatically generated mpi-tkr-sizeof.* Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2016-10-28 04:41:20 +03:00
ompi/mpi/fortran/use-mpi-tkr/mpi-tkr-sizeof.f90
ompi/mpi/fortran/use-mpi-tkr/mpi-tkr-sizeof.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/java/java/mpi
ompi/mpi/java/java/*.jar
ompi/mpi/java/java/*.h
ompi/mpi/java/java/doc
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/man/man3/MPI*.3
ompi/mpi/man/man3/OpenMPI.3
ompi/mpi/man/man3/.dir-stamp
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpi/tool/profile/*.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpiext/affinity/c/OMPI_Affinity_str.3
ompi/mpiext/affinity/c/example
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/mpiext/example/tests/progress_c
ompi/mpiext/example/tests/progress_mpifh
ompi/mpiext/example/tests/progress_usempi
ompi/mpiext/example/tests/progress_usempif08
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
.gitignore: add man page in CUDA extension
2015-08-06 16:49:33 +03:00
ompi/mpiext/cuda/c/MPIX_Query_cuda_support.3
Update ignores
2015-08-15 17:56:31 +03:00
ompi/mpiext/cuda/c/mpiext_cuda_c.h
Update ignores Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-11-27 22:04:36 +03:00
ompi/mpiext/cuda/c/cuda_c.h
.gitignore: add man page in CUDA extension
2015-08-06 16:49:33 +03:00
mpiext/pcollreq: Add `MPIX_Bcast_init` etc. Until the MPI Forum decides to add the persistent collective communication request feature to the MPI Standard, these functions are supported through MPI extensions with the `MPIX_` prefix. Only C bindings are supported currently. Signed-off-by: KAWASHIMA Takahiro <t-kawashima@jp.fujitsu.com>
2017-01-19 04:28:28 +03:00
ompi/mpiext/pcollreq/c/MPIX_*.3
Add a bunch of missing ignores Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-07-26 02:13:08 +03:00
ompi/mpiext/pcollreq/c/profile/pallgather_init.c
ompi/mpiext/pcollreq/c/profile/pallgatherv_init.c
ompi/mpiext/pcollreq/c/profile/pallreduce_init.c
ompi/mpiext/pcollreq/c/profile/palltoall_init.c
ompi/mpiext/pcollreq/c/profile/palltoallv_init.c
ompi/mpiext/pcollreq/c/profile/palltoallw_init.c
ompi/mpiext/pcollreq/c/profile/pbarrier_init.c
ompi/mpiext/pcollreq/c/profile/pbcast_init.c
ompi/mpiext/pcollreq/c/profile/pexscan_init.c
ompi/mpiext/pcollreq/c/profile/pgather_init.c
ompi/mpiext/pcollreq/c/profile/pgatherv_init.c
ompi/mpiext/pcollreq/c/profile/pmpiext_pcollreq_c.h
ompi/mpiext/pcollreq/c/profile/pneighbor_allgather_init.c
ompi/mpiext/pcollreq/c/profile/pneighbor_allgatherv_init.c
ompi/mpiext/pcollreq/c/profile/pneighbor_alltoall_init.c
ompi/mpiext/pcollreq/c/profile/pneighbor_alltoallv_init.c
ompi/mpiext/pcollreq/c/profile/pneighbor_alltoallw_init.c
ompi/mpiext/pcollreq/c/profile/preduce_init.c
ompi/mpiext/pcollreq/c/profile/preduce_scatter_block_init.c
ompi/mpiext/pcollreq/c/profile/preduce_scatter_init.c
ompi/mpiext/pcollreq/c/profile/pscan_init.c
ompi/mpiext/pcollreq/c/profile/pscatter_init.c
ompi/mpiext/pcollreq/c/profile/pscatterv_init.c
Update ignores Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-11-27 22:04:36 +03:00
ompi/mpiext/pcollreq/c/profile/ppcollreq_c.h
mpiext/pcollreq: Add `MPIX_Bcast_init` etc. Until the MPI Forum decides to add the persistent collective communication request feature to the MPI Standard, these functions are supported through MPI extensions with the `MPIX_` prefix. Only C bindings are supported currently. Signed-off-by: KAWASHIMA Takahiro <t-kawashima@jp.fujitsu.com>
2017-01-19 04:28:28 +03:00
Update ignores Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-08-03 18:51:36 +03:00
ompi/mpiext/pcollreq/mpif-h/profile/pallgather_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pallgatherv_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pallreduce_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/palltoall_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/palltoallv_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/palltoallw_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pbarrier_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pbcast_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pexscan_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pgather_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pgatherv_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pneighbor_allgather_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pneighbor_allgatherv_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pneighbor_alltoall_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pneighbor_alltoallv_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pneighbor_alltoallw_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/preduce_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/preduce_scatter_block_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/preduce_scatter_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pscan_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pscatter_init_f.c
ompi/mpiext/pcollreq/mpif-h/profile/pscatterv_init_f.c
mpiext/shortfloat: Add `shortfloat` MPI extension This extension provides additional MPI datatypes `MPIX_SHORT_FLOAT`, `MPIX_C_SHORT_FLOAT_COMPLEX`, and `MPIX_CXX_SHORT_FLOAT_COMPLEX` for `short float` (C/C++), `short float _Complex` (C), and `std::complex<short float>` (C++), respectively, or their alternate types like `_Float16`. See `ompi/mpiext/shortfloat/README.txt` for details. Signed-off-by: KAWASHIMA Takahiro <t-kawashima@jp.fujitsu.com>
2018-11-22 15:22:25 +03:00
ompi/mpiext/shortfloat/c/mpiext_shortfloat_c.h
ompi/mpiext/shortfloat/mpif-h/mpiext_shortfloat_mpifh.h
ompi/mpiext/shortfloat/use-mpi-f08/mpiext_shortfloat_usempif08.h
Update git/hg ignore files This commit was SVN r32739.
2014-09-16 09:00:23 +04:00
ompi/tools/mpisync/mpisync
ompi/tools/mpisync/mpirun_prof
ompi/tools/mpisync/ompi_timing_post
Cleanup timing macros for portability across compilers. Rename the --enable-timing configure option to be --enable-pmix-timing so it doesn't pickup external timing requests. Remove a stale function reference in PMIx so it can compile with timing enabled. Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2017-04-07 22:15:46 +03:00
ompi/tools/mpisync/mpisync.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/tools/ompi_info/ompi_info
ompi/tools/ompi_info/ompi_info.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/tools/wrappers/mpic++-wrapper-data.txt
ompi/tools/wrappers/mpicc-wrapper-data.txt
ompi/tools/wrappers/mpifort-wrapper-data.txt
ompi/tools/wrappers/mpicc.1
ompi/tools/wrappers/mpic++.1
ompi/tools/wrappers/mpicxx.1
ompi/tools/wrappers/mpifort.1
java: Use correct date/version in `mpijava` man page `mpijavac.1` should be generated at `make`-time... Signed-off-by: KAWASHIMA Takahiro <t-kawashima@jp.fujitsu.com>
2017-05-31 08:17:44 +03:00
ompi/tools/wrappers/mpijavac.1
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
ompi/tools/wrappers/ompi_wrapper_script
ompi/tools/wrappers/ompi.pc
ompi/tools/wrappers/ompi-c.pc
ompi/tools/wrappers/ompi-cxx.pc
ompi/tools/wrappers/ompi-fort.pc
ompi/tools/wrappers/mpijavac.pl
ompi/tools/wrappers/mpif90.1
ompi/tools/wrappers/mpif77.1
ompi/tools/wrappers/mpicxx-wrapper-data.txt
ompi/tools/wrappers/mpif77-wrapper-data.txt
ompi/tools/wrappers/mpif90-wrapper-data.txt
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/libltdl
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/asm/atomic-asm.S
opal/asm/atomic-test
opal/asm/generated/atomic-*.s
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/include/opal_config.h
opal/include/opal_config.h.in
opal/include/opal/install_dirs.h
opal/include/opal/version.h
opal/include/opal/frameworks.h
opal/include/opal/sys/powerpc/atomic-32.s
opal/include/opal/sys/powerpc/atomic-64.s
opal/include/opal/sys/powerpc/atomic-32-64.s
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/mca/base/mca_base_parse_paramfile_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
libfabric configury: make AC_CONFIG_FILES be unconditional Also add the generated config.h file to .gitignore.
2014-12-20 19:30:32 +03:00
opal/mca/common/libfabric/libfabric/config.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update git/hg ignore files This commit was SVN r32320.
2014-07-26 09:00:28 +04:00
opal/mca/btl/openib/btl_openib_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
.gitignore: ignore usnic unit test executable
2014-12-04 01:20:33 +03:00
opal/mca/btl/usnic/usnic_btl_run_tests
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/mca/crs/opal_crs.7
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
gitignore: even more regexp ignores Simple regexps to always ignore the hwloc/libevent stuff, regardless of their specific version. Yay regexps!
2014-12-20 04:44:26 +03:00
opal/mca/event/libevent*/libevent/config.h.in
opal/mca/event/libevent*/libevent/config.h
opal/mca/event/libevent*/libevent/libevent.pc
opal/mca/event/libevent*/libevent/libevent_openssl.pc
opal/mca/event/libevent*/libevent/libevent_pthreads.pc
opal/mca/event/libevent*/libevent/include/event2/event-config.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
gitignore: even more regexp ignores Simple regexps to always ignore the hwloc/libevent stuff, regardless of their specific version. Yay regexps!
2014-12-20 04:44:26 +03:00
opal/mca/hwloc/hwloc*/hwloc/include/hwloc/autogen/config.h
opal/mca/hwloc/hwloc*/hwloc/include/private/autogen/config.h
Remove build product and update .gitignore to avoid picking it up again Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2017-07-20 21:49:48 +03:00
opal/mca/hwloc/base/static-components.h.new.extern
opal/mca/hwloc/base/static-components.h.new.struct
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/mca/installdirs/config/install_dirs.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
pmix/pmix4x: refresh to the latest open PMIx master refresh to openpmix/openpmix@ea3b29b1a4d35c63d99a84a09389ddddb2a4b7c6 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2019-10-01 07:36:51 +03:00
!opal/mca/pmix/pmix*/openpmix/AUTHORS
!opal/mca/pmix/pmix*/openpmix/contrib/perf_tools/Makefile
opal/mca/pmix/pmix*/openpmix/include/pmix/autogen/config.h
opal/mca/pmix/pmix*/openpmix/include/pmix/autogen/config.h.in
opal/mca/pmix/pmix*/openpmix/src/include/private/autogen/config.h.in
opal/mca/pmix/pmix*/openpmix/src/include/private/autogen/config.h
opal/mca/pmix/pmix*/openpmix/src/include/frameworks.h
opal/mca/pmix/pmix*/openpmix/src/mca/pinstalldirs/config/pinstall_dirs.h
opal/mca/pmix/pmix*/openpmix/config/autogen_found_items.m4
opal/mca/pmix/pmix*/openpmix/config/mca_library_paths.txt
opal/mca/pmix/pmix*/openpmix/config/test-driver
opal/mca/pmix/pmix*/openpmix/src/include/pmix_config.h
opal/mca/pmix/pmix*/openpmix/src/include/pmix_config.h.in
opal/mca/pmix/pmix*/openpmix/include/pmix_common.h
opal/mca/pmix/pmix*/openpmix/include/pmix_rename.h
opal/mca/pmix/pmix*/openpmix/include/pmix_version.h
opal/mca/pmix/pmix*/openpmix/src/util/keyval/keyval_lex.c
opal/mca/pmix/pmix*/openpmix/src/util/show_help_lex.c
opal/mca/pmix/pmix*/openpmix/examples/alloc
opal/mca/pmix/pmix*/openpmix/examples/client
opal/mca/pmix/pmix*/openpmix/examples/debugger
opal/mca/pmix/pmix*/openpmix/examples/debuggerd
opal/mca/pmix/pmix*/openpmix/examples/dmodex
opal/mca/pmix/pmix*/openpmix/examples/dynamic
opal/mca/pmix/pmix*/openpmix/examples/fault
opal/mca/pmix/pmix*/openpmix/examples/jctrl
opal/mca/pmix/pmix*/openpmix/examples/pub
opal/mca/pmix/pmix*/openpmix/examples/server
opal/mca/pmix/pmix*/openpmix/examples/tool
opal/mca/pmix/pmix*/openpmix/test/run_tests00.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests01.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests02.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests03.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests04.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests05.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests06.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests07.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests08.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests09.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests10.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests11.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests12.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests13.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests14.pl
opal/mca/pmix/pmix*/openpmix/test/run_tests15.pl
Update IOF redirection options Provide both "--output-directory" and "--output-filename" options but do not allow both to be given at the same time. Output-directory allows specification of a directory, with output redirected into files of form "<directory>/<jobid>/rank.<vpid>/stdout[err]". This option also supports two directives: nojobid (removes the jobid directory layer) and nocopy (do not copy the output to the terminal). Output-filename is the "old" behavior that names the output files as "<filename>.rank" with both stdout and stderr redirected into it. This option only supports one directive: nocopy (do not copy the output to the terminal). Fix both the --help and man documentation. Signed-off-by: Ralph Castain <rhc@pmix.org>
2019-11-13 22:36:43 +03:00
opal/mca/pmix/pmix*/openpmix/src/tools/wrapper/pmix.pc
opal/mca/pmix/pmix*/openpmix/src/tools/wrapper/pmixcc-wrapper-data.txt
pmix/pmix4x: update .gitignore Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2019-04-22 03:54:34 +03:00
Add pmix120 component, update the error handling functions in the PMIx API. Update the configure logic for the new pmix120 component ckpt Get the pmix120 component to work - still not really registering or handling notifications, but infrastructure now operates Cleanup some of the symbol scopes, and provide a more comprehensive rename.h file. Will pretty it up later - let's see how this works Cleanup the rename files to use the pretty macros
2015-12-17 06:06:47 +03:00
Update master to PMIx v4 Retain ext3x for PMIx 3 compatibility Get the blasted permissions correct on config files Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-09-13 05:20:24 +03:00
opal/mca/pmix/ext4x/ext4x.c
opal/mca/pmix/ext4x/ext4x.h
opal/mca/pmix/ext4x/ext4x_client.c
opal/mca/pmix/ext4x/ext4x_component.c
opal/mca/pmix/ext4x/ext4x_server_north.c
opal/mca/pmix/ext4x/ext4x_server_south.c
Update ignores for pmix/ext3x component Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-01-31 08:41:55 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/tools/opal-checkpoint/opal-checkpoint
opal/tools/opal-checkpoint/opal-checkpoint.1
opal/tools/opal-restart/opal-restart
opal/tools/opal-restart/opal-restart.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/tools/wrappers/opalcc-wrapper-data.txt
opal/tools/wrappers/opalc++-wrapper-data.txt
opal/tools/wrappers/opalCC-wrapper-data.txt
opal/tools/wrappers/opal_wrapper
opal/tools/wrappers/opalcc.1
opal/tools/wrappers/opalc++.1
opal/tools/wrappers/generic_wrapper.1
opal/tools/wrappers/opal_wrapper.1
opal/tools/wrappers/opal.pc
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
opal/util/show_help_lex.c
opal/util/keyval/keyval_lex.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Clean out ORTE references from .gitignore Signed-off-by: Ralph Castain <rhc@pmix.org>
2020-02-23 00:24:18 +03:00
test/simple/abort
test/simple/accept
test/simple/attach
test/simple/bad_exit
test/simple/bcast_loop
test/simple/binding
test/simple/concurrent_spawn
test/simple/connect
test/simple/crisscross
test/simple/delayed_abort
test/simple/hello_barrier
test/simple/hello_nodename
test/simple/hello_output
test/simple/hello_show_help
test/simple/hello
test/simple/hello++
test/simple/interlib
test/simple/loop_child
test/simple/loop_spawn
test/simple/mpi_barrier
test/simple/mpi_no_op
test/simple/mpi_spin
test/simple/multi_abort
test/simple/parallel_r8
test/simple/parallel_r64
test/simple/parallel_w8
test/simple/parallel_w64
test/simple/pinterlib
test/simple/pmix
test/simple/pubsub
test/simple/read_write
test/simple/reduce-hang
test/simple/ring
test/simple/segv
test/simple/simple_spawn
test/simple/slave
test/simple/spawn_multiple
test/simple/xlib
test/simple/ziaprobe
test/simple/ziatest
test/simple/*.dwarf
test/simple/junk*
test/simple/sio
test/simple/sendrecv_blaster
test/simple/early_abort
test/simple/spawn_problem/ch_rec
test/simple/spawn_problem/output
test/simple/spawn_problem/start
test/simple/debugger
test/simple/server_port_name.txt
test/simple/singleton_client_server
test/simple/intercomm_create
test/simple/spawn_tree
test/simple/init-exit77
test/simple/mpi_info
test/simple/info_spawn
test/simple/client
test/simple/server
test/simple/paccept
test/simple/pconnect
test/simple/thread_init
test/simple/memcached-dummy
test/simple/coll_test
test/simple/badcoll
test/simple/iof
test/simple/no-disconnect
test/simple/nonzero
test/simple/add_host
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/include/shmem.h
oshmem/include/shmem_portable_platform.h
oshmem/include/oshmem/frameworks.h
oshmem/include/oshmem/version.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/mca/sshmem/base/static-components.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/shmem/c/profile/p*.c
oshmem/shmem/c/profile/*.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/shmem/fortran/libshmem_fortran.la
Update git/hg ignore files This commit was SVN r31563.
2014-04-30 09:00:33 +04:00
oshmem/shmem/fortran/profile/pshmem_*_f.c
Update git/hg ignore files This commit was SVN r31581.
2014-05-01 09:00:32 +04:00
oshmem/shmem/fortran/profile/pshpdeallc_f.c
oshmem/shmem/fortran/profile/pshpclmove_f.c
oshmem/shmem/fortran/profile/pmy_pe_f.c
oshmem/shmem/fortran/profile/pshpalloc_f.c
oshmem/shmem/fortran/profile/pnum_pes_f.c
oshmem/shmem/fortran/profile/pstart_pes_f.c
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update git/hg ignore files This commit was SVN r31813.
2014-05-19 09:00:28 +04:00
oshmem/shmem/java/java/shmem.jar
oshmem/shmem/java/java/doc
oshmem/shmem/java/java/shmem_Constant.h
oshmem/shmem/java/java/shmem_ShMem.h
oshmem/shmem/java/java/shmem
oshmem/shmem/java/java/shmem_Addr.h
Update git/hg ignore files This commit was SVN r31925.
2014-06-02 09:00:30 +04:00
oshmem/shmem/java/java/shmem_PSync.h
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
oshmem: Add man related files into gitignore Signed-off-by: Igor Ivanov <Igor.Ivanov@itseez.com>
2015-08-25 13:04:44 +03:00
oshmem/shmem/man/man3/shmem_*.3
oshmem/shmem/man/man3/OpenSHMEM.3
oshmem/shmem/man/man3/intro_shmem.3
oshmem/shmem/man/man3/_my_pe.3
oshmem/shmem/man/man3/_num_pes.3
oshmem/shmem/man/man3/shfree.3
oshmem/shmem/man/man3/shmalloc.3
oshmem/shmem/man/man3/shmemalign.3
oshmem/shmem/man/man3/shrealloc.3
oshmem/shmem/man/man3/start_pes.3
oshmem/shmem/man/man3/.dir-stamp
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/tools/oshmem_info/oshmem_info
oshmem/tools/oshmem_info/oshmem_info.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Update ignores for new oshmem man pages
2015-10-13 03:30:12 +03:00
oshmem/tools/wrappers/oshcc.1
oshmem/tools/wrappers/oshfort.1
oshmem/tools/wrappers/oshrun.1
oshmem/tools/wrappers/shmemcc.1
oshmem/tools/wrappers/shmemfort.1
oshmem/tools/wrappers/shmemrun.1
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
oshmem/tools/wrappers/shmemcc-wrapper-data.txt
oshmem/tools/wrappers/shmemfort-wrapper-data.txt
git: Ignore OSHMEM C++ wrapper artifacts Signed-off-by: Brian Barrett <bbarrett@amazon.com>
2017-09-08 18:03:27 +03:00
oshmem/tools/wrappers/oshCC.1
oshmem/tools/wrappers/oshc++.1
oshmem/tools/wrappers/oshcxx.1
oshmem/tools/wrappers/shmemCC.1
oshmem/tools/wrappers/shmemc++-wrapper-data.txt
oshmem/tools/wrappers/shmemc++.1
oshmem/tools/wrappers/shmemcxx.1
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/asm/atomic_math_noinline
test/asm/atomic_barrier
test/asm/atomic_cmpset_noinline
test/asm/atomic_math
test/asm/atomic_cmpset
test/asm/atomic_spinlock_noinline.c
test/asm/atomic_barrier_noinline.c
test/asm/atomic_math_noinline.c
test/asm/atomic_cmpset_noinline.c
test/asm/atomic_spinlock_noinline
test/asm/atomic_barrier_noinline
test/asm/atomic_spinlock
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/class/*.txt
test/class/ompi_bitmap_test_out.txt
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/ompi_circular_buffer_fifo
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/class/ompi_fifo
test/class/ompi_rb_tree
test/class/ompi_bitmap
test/class/opal_bitmap
.gitignore: ignore executes for new tests
2014-12-11 21:02:10 +03:00
test/class/opal_fifo
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/opal_hash_table
.gitignore: ignore executes for new tests
2014-12-11 21:02:10 +03:00
test/class/opal_lifo
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/opal_list
test/class/opal_pointer_array
test/class/opal_proc_table
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/class/opal_tree
.gitignore: add a missing test executable Also alphebetize the ignored files in test/class.
2014-12-01 21:56:11 +03:00
test/class/opal_value_array
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/datatype/ddt_test
test/datatype/ddt_pack
.gitignore: add test executable to ignore Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2016-08-17 14:27:51 +03:00
test/datatype/external32
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/datatype/to_self
test/datatype/checksum
test/datatype/position
test/datatype/ddt_raw
test/datatype/opal_datatype_test
.gitignore: add more test executables to be ignored
2014-11-22 02:08:36 +03:00
test/datatype/position_noncontig
test/datatype/unpack_ooo
Silence warnings in optimized build Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2017-12-20 23:00:28 +03:00
test/datatype/unpack_hetero
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/dss/dss_buffer
test/dss/dss_copy
test/dss/dss_size
test/dss/dss_cmp
test/dss/dss_release
test/dss/dss_payload
test/dss/dss_set_get
test/dss/dss_print
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/event/signal-test
test/event/event-test
test/event/time-test
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Fix a convertion problem and add a comment about the lack of component retain in the new component infrastructure. Clean Makefile.am to fix "make distcheck". Update the gitignore rules.
2015-07-25 22:15:54 +03:00
test/monitoring/monitoring_test
Update ignores Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2017-06-27 19:07:19 +03:00
test/monitoring/check_monitoring
test/monitoring/example_reduce_count
test/monitoring/test_overhead
test/monitoring/test_pvar_access
Fix a convertion problem and add a comment about the lack of component retain in the new component infrastructure. Clean Makefile.am to fix "make distcheck". Update the gitignore rules.
2015-07-25 22:15:54 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/mpi/environment/chello
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/runtime/parse_context
test/runtime/sigchld
test/runtime/start_shut
test/runtime/opal_init_finalize
test/runtime/orte_init_finalize
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Silence warnings and ignore test binary Signed-off-by: Ralph Castain <rhc@open-mpi.org>
2018-06-15 21:32:22 +03:00
test/spc/spc_test
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/threads/opal_condition
test/threads/opal_thread
gitignore: minor updates, add whitespace Add new file from modern versions of GNU autotools, remove some duplicates, and add some whitespace to make the file easier to read.
2015-01-22 04:14:47 +03:00
Replace top-level .gitignore with .gitignore_global, and add .hgignore_global The rationale for this name switch is as follows: 0. These two files will be automatically kept up-to-date with svn:ignore properties in the tree via a cron script. Meaning: if a developer makes changes to svn:ignore properties, those changes will automatically be reflected in .gitignore_global / .hgignore_global within a fixed time period (at the moment, nightly). 1. Developers who make pure clones of git/hg OMPI repos can copy the relevant .*ignore_global file to .*ignore. This gives them a good starting point for a fully-populated ignore file. However, since the upstream _global file may change over time, developers will likely want to keep them in sync with their local .*ignore file. Here's two possibilities: 1a. Maintain a single .*ignore file and manually merge in changes from the _global file upstream. 1b. Maintain their local ignores in a .*ignore_local file, and periodically "cat .*ignore_global .*ignore_local > *.ignore" (e.g., whenever the upstream _global file changes). 2. Developers who make svn+clone checkouts can do similar things as listed in 1, with the added feature that they cannot make the mistake of committing their locally-modified .*ignore file back to SVN (presumably containing references to files that do not exist in SVN), since the .*ignore file is not in SVN. Point #2 is probably the stronger of these two reasons -- prevent mistakes of developers accidentally committing locally-modified .*ignore files back to SVN. This commit was SVN r31408.
2014-04-16 02:24:44 +04:00
test/util/aaa
test/util/test_session_dir_out
test/util/opal_os_path
test/util/opal_argv
test/util/opal_os_create_dirpath
test/util/opal_if
test/util/opal_error
test/util/opal_timer
test/util/orte_sys_info
test/util/orte_session_dir
test/util/orte_sys_info
test/util/orte_universe_setup_file_io
test/util/opal_basename
test/util/ompi_numtostr
test/util/ompi_pack
test/util/test-file
test/util/opal_sos
test/util/opal_path_nfs
test/util/opal_path_nfs.out
test/util/opal_bit_ops
util: move graph solver from usnic to util Cisco wrote a bipartite graph solver to properly solve interface pair selection for usNIC. Using the reachable framework, the TCP BTL (and possibly the runtime network code) can use the graph solver to make more optimal pair selection. Jeff was happy to have the code more broadly used, but didn't have time to do the move, hence this commit. There are a couple of minor changes to the code compared to the usNIC version. Obviously, the functions have been renamed to match naming convention for their new home. Since it's easier to write unit tests for util/ code, the unit tests have been made first class tests run at "make check" time. This last bit required moving some of the definitions into a new header, bipartite_graph_internal.h, so that they could be included in both the library code and the test code. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
2017-09-14 21:36:48 +03:00
test/util/bipartite_graph
reachable: add tests Add test suite for netlink and weighted reachable components. We don't have a great way of running components through unit tests today, so make them stand-alone tests that are run with mpirun and such. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
2017-07-29 03:00:40 +03:00
opal/test/reachable/reachable_netlink
opal/test/reachable/reachable_weighted
Копировать постоянную ссылку