Open and close the memcpy component. Hopefully it is in the right place, as

the memcpy should be available as soon as possible after startup.

This commit was SVN r9533.

opal/runtime/opal_finalize.c

@@ -30,6 +30,7 @@
 #include "opal/mca/base/base.h"
 #include "opal/runtime/opal.h"
 #include "opal/constants.h"
+#include "opal/mca/memcpy/base/base.h"
 #include "opal/mca/memory/base/base.h"
 #include "opal/mca/timer/base/base.h"
 #include "opal/mca/paffinity/base/base.h"
@@ -86,6 +87,9 @@ opal_finalize(void)
     /* close the processor affinity base */
     opal_paffinity_base_close();
 
+    /* close the memcpy base */
+    opal_memcpy_base_close();
+
     /* finalize the mca */
     mca_base_close();
 

opal/runtime/opal_init.c

@@ -28,6 +28,7 @@
 #include "opal/mca/base/base.h"
 #include "opal/runtime/opal.h"
 #include "opal/mca/memory/base/base.h"
+#include "opal/mca/memcpy/base/base.h"
 #include "opal/mca/paffinity/base/base.h"
 #include "opal/mca/timer/base/base.h"
 #include "opal/constants.h"
@@ -192,6 +193,15 @@ opal_init(void)
     opal_paffinity_base_open();
     opal_paffinity_base_select();
 
+    /* the memcpy component should be one of the first who get
+     * loaded in order to make sure we ddo have all the available
+     * versions of memcpy correctly configured.
+     */
+    if( OPAL_SUCCESS != (ret = opal_memcpy_base_open()) ) {
+        error = "opal_memcpy_base_open";
+        goto return_error;
+    }
+
     /* open the memory manager components.  Memory hooks may be
        triggered before this (any time after mem_free_init(),
        actually).  This is a hook available for memory manager hooks