Ralph Castain f424aa367e Fix external PMIx v1.2.5 support ...

As @hjelmn and I discussed, this is a little hacky. However, it is the only solution that can be done solely from the OMPI side.

Signed-off-by: Ralph Castain <rhc@open-mpi.org>

2018-04-25 13:42:36 -07:00

..

class

opal_free_list: use lifo atomic functions in opal_free_list_wait_mt

2018-03-26 10:16:42 -06:00

datatype

opal_datatype_module.c: reset opal_cuda_verbose

2018-03-13 10:10:15 -07:00

dss

Update ORTE to support PMIx v3

2018-03-02 02:00:31 -08:00

etc

Correct the comment in the default MCA param template - we do not support a param called "component_path". The correct syntax is "mca_base_component_path"

2018-01-05 08:46:44 -08:00

include

Update ORTE to support PMIx v3

2018-03-02 02:00:31 -08:00

mca

Fix external PMIx v1.2.5 support

2018-04-25 13:42:36 -07:00

memoryhooks

opal: rename opal_atomic_init to opal_atomic_lock_init

2017-08-07 14:15:11 -06:00

runtime

timings: added new timing points

2018-03-21 05:16:25 +02:00

test/reachable

reachable: add tests

2017-09-19 19:42:54 -07:00

threads

opal/asm: add fetch-and-op atomics

2017-11-30 10:41:23 -07:00

tools

Revert "Update to sync with OMPI master and cleanup to build"

2016-11-22 15:03:20 -08:00

util

Merge pull request #4933 from karasevb/timings_update

2018-03-25 00:10:49 -07:00

win32

opal: standardize on max hostname length

2016-04-24 08:19:47 +02:00

common_sym_whitelist.txt

opal: add code patcher framework

2016-04-13 17:16:13 -06:00

Makefile.am

opal: remove generated asm code

2017-08-03 09:18:58 -06:00

win_makefile

Purge whitespace from the repo

2015-06-23 20:59:57 -07:00