ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
openmpi/opal/mca/memcpy/configure.m4

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

The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
dnl -*- shell-script -*-
dnl
dnl Copyright (c) 2004-2006 The University of Tennessee and The University
dnl of Tennessee Research Foundation. All rights
dnl reserved.
* AC_CONFIG_LINKS has a minor problem in that it always uses ln -s, rather than $(LN_S). This causes problems with with Windows and probably elsewhere (re: #200). So use a slightly different trick to get the right header selected for the MEMCPY and TIMER components. * Using the same trick used to solve the AC_CONFIG_LINKS problem, stop using a separate header file for direct calling in the PML and MTL. This lets me remove some icky code in ompi_mca.m4 that was more fragile than I really liked. This commit was SVN r10841.
2006-07-16 04:23:52 +00:00
dnl Copyright (c) 2004-2006 The Regents of the University of California.
dnl All rights reserved.
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
dnl $COPYRIGHT$
Purge whitespace from the repo
2015-06-23 20:59:57 -07:00
dnl
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
dnl Additional copyrights may follow
Purge whitespace from the repo
2015-06-23 20:59:57 -07:00
dnl
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
dnl $HEADER$
dnl
* AC_CONFIG_LINKS has a minor problem in that it always uses ln -s, rather than $(LN_S). This causes problems with with Windows and probably elsewhere (re: #200). So use a slightly different trick to get the right header selected for the MEMCPY and TIMER components. * Using the same trick used to solve the AC_CONFIG_LINKS problem, stop using a separate header file for direct calling in the PML and MTL. This lets me remove some icky code in ompi_mca.m4 that was more fragile than I really liked. This commit was SVN r10841.
2006-07-16 04:23:52 +00:00
dnl we only want one
WARNING: Work on the temp branch being merged here encountered problems with bugs in subversion. Considerable effort has gone into validating the branch. However, not all conditions can be checked, so users are cautioned that it may be advisable to not update from the trunk for a few days to allow MTT to identify platform-specific issues. This merges the branch containing the revamped build system based around converting autogen from a bash script to a Perl program. Jeff has provided emails explaining the features contained in the change. Please note that configure requirements on components HAVE CHANGED. For example. a configure.params file is no longer required in each component directory. See Jeff's emails for an explanation. This commit was SVN r23764.
2010-09-17 23:04:06 +00:00
m4_define(MCA_opal_memcpy_CONFIGURE_MODE, STOP_AT_FIRST)
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
WARNING: Work on the temp branch being merged here encountered problems with bugs in subversion. Considerable effort has gone into validating the branch. However, not all conditions can be checked, so users are cautioned that it may be advisable to not update from the trunk for a few days to allow MTT to identify platform-specific issues. This merges the branch containing the revamped build system based around converting autogen from a bash script to a Perl program. Jeff has provided emails explaining the features contained in the change. Please note that configure requirements on components HAVE CHANGED. For example. a configure.params file is no longer required in each component directory. See Jeff's emails for an explanation. This commit was SVN r23764.
2010-09-17 23:04:06 +00:00
AC_DEFUN([MCA_opal_memcpy_CONFIG],[
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
memcpy_base_include=
# first, compile all the components
Add ability to completely turn off MPI one-sided support, so that users can experiment with using ROMIO directly. This commit was SVN r15922.
2007-08-18 21:35:51 +00:00
MCA_CONFIGURE_FRAMEWORK($1, $2, 1)
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
# someone should have set this...
if test "$memcpy_base_include" = "" ; then
memcpy_base_include="base/memcpy_base_default.h"
fi
* AC_CONFIG_LINKS has a minor problem in that it always uses ln -s, rather than $(LN_S). This causes problems with with Windows and probably elsewhere (re: #200). So use a slightly different trick to get the right header selected for the MEMCPY and TIMER components. * Using the same trick used to solve the AC_CONFIG_LINKS problem, stop using a separate header file for direct calling in the PML and MTL. This lets me remove some icky code in ompi_mca.m4 that was more fragile than I really liked. This commit was SVN r10841.
2006-07-16 04:23:52 +00:00
AC_DEFINE_UNQUOTED([MCA_memcpy_IMPLEMENTATION_HEADER],
["opal/mca/memcpy/$memcpy_base_include"],
[Header to include for memcpy implementation])
The memcpy framework. The base component is here, but right now no implementations. I dont want to overload the memcpy functions, therefore people interested in using the high performance memcpy should use directly opal_memcpy instead. Notice, that there are 2 other versions of memcpy available, which use a destination or a source described as iovecs. This commit was SVN r9532.
2006-04-05 05:56:08 +00:00
])
Копировать постоянную ссылку