Ralph Castain 45af6cf59e The move of the orte_db framework to opal required that we create an opaque opal_identifier_t type as OPAL cannot know anything about the ORTE process name. However, passing a value down to opal and then having the db components reference it causes alignment issues on Solaris Sparc platforms. So pass the pointer instead and do the old "memcpy" trick to avoid the problem. ... This commit was SVN r28308.		2013-04-08 23:34:16 +00:00
..
configure.m4	Move the RTE framework change into the trunk. With this change, all non-CR	2013-01-27 23:25:10 +00:00
Makefile.am	Fix double-install issue when --with-devel-headers is used	2013-01-29 17:23:18 +00:00
rte_orte_component.c	Move the RTE framework change into the trunk. With this change, all non-CR	2013-01-27 23:25:10 +00:00
rte_orte_module.c	The move of the orte_db framework to opal required that we create an opaque opal_identifier_t type as OPAL cannot know anything about the ORTE process name. However, passing a value down to opal and then having the db components reference it causes alignment issues on Solaris Sparc platforms. So pass the pointer instead and do the old "memcpy" trick to avoid the problem.	2013-04-08 23:34:16 +00:00
rte_orte.h	Per the meeting on moving the BTLs to OPAL, move the ORTE database "db" framework to OPAL so the relocated BTLs can access it. Because the data is indexed by process, this requires that we define a new "opal_identifier_t" that corresponds to the orte_process_name_t struct. In order to support multiple run-times, this is defined in opal/mca/db/db_types.h as a uint64_t without identifying the meaning of any part of that data.	2013-02-26 17:50:04 +00:00