RepoMirrors
/
ceph
mirror of https://github.com/ceph/ceph
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ceph/cmake/modules/SIMDExt.cmake

111 lines
3.4 KiB
CMake
Raw Normal View History

cmake: fix typos Signed-off-by: Kefu Chai <kchai@redhat.com>
2018-09-18 03:19:53 +00:00
# detect SIMD extensions
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
#
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
# HAVE_ARM
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
# HAVE_ARMV8_CRC
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
# HAVE_ARMV8_CRC_CRYPTO_INTRINSICS
# HAVE_ARMV8_CRYPTO
erasure-code: Remove SIMD flavors for jerasure and shec By switching to a new gf-complete with SIMD runtime detection, we can now remove all the different flavors of jerasure and shec. This simplifies deployment and configuration of erasure coding, enables hetergenous OSDs, and enables us to take advantage of new performance improvements in jerasure without config/build changes. This commit removes flavors from cmake, removes ErasureCodePluginSelect___, and fixes unit tests. There is now a single plugin for jerasure and a single plugin for shec. SIMDExt.cmake was changed so that its a little more generic, and is not polluted with gf-complete specific CFLAG defines. The #define for SIMD instruction were based on gf-complete. I also added a small init helper for jerasure that has code that was common between jerasure and shec. Signed-off-by: Bassam Tabbara <bassam.tabbara@quantum.com>
2016-09-22 19:40:52 +00:00
# HAVE_ARMV8_SIMD
# HAVE_ARM_NEON
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
#
# HAVE_INTEL
erasure-code: Remove SIMD flavors for jerasure and shec By switching to a new gf-complete with SIMD runtime detection, we can now remove all the different flavors of jerasure and shec. This simplifies deployment and configuration of erasure coding, enables hetergenous OSDs, and enables us to take advantage of new performance improvements in jerasure without config/build changes. This commit removes flavors from cmake, removes ErasureCodePluginSelect___, and fixes unit tests. There is now a single plugin for jerasure and a single plugin for shec. SIMDExt.cmake was changed so that its a little more generic, and is not polluted with gf-complete specific CFLAG defines. The #define for SIMD instruction were based on gf-complete. I also added a small init helper for jerasure that has code that was common between jerasure and shec. Signed-off-by: Bassam Tabbara <bassam.tabbara@quantum.com>
2016-09-22 19:40:52 +00:00
# HAVE_INTEL_SSE
# HAVE_INTEL_SSE2
# HAVE_INTEL_SSE3
# HAVE_INTEL_SSSE3
# HAVE_INTEL_PCLMUL
# HAVE_INTEL_SSE4_1
# HAVE_INTEL_SSE4_2
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
#
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
# HAVE_PPC64LE
# HAVE_PPC64
# HAVE_PPC
#
erasure-code: Remove SIMD flavors for jerasure and shec By switching to a new gf-complete with SIMD runtime detection, we can now remove all the different flavors of jerasure and shec. This simplifies deployment and configuration of erasure coding, enables hetergenous OSDs, and enables us to take advantage of new performance improvements in jerasure without config/build changes. This commit removes flavors from cmake, removes ErasureCodePluginSelect___, and fixes unit tests. There is now a single plugin for jerasure and a single plugin for shec. SIMDExt.cmake was changed so that its a little more generic, and is not polluted with gf-complete specific CFLAG defines. The #define for SIMD instruction were based on gf-complete. I also added a small init helper for jerasure that has code that was common between jerasure and shec. Signed-off-by: Bassam Tabbara <bassam.tabbara@quantum.com>
2016-09-22 19:40:52 +00:00
# SIMD_COMPILE_FLAGS
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
#
if(CMAKE_SYSTEM_PROCESSOR MATCHES "aarch64|AARCH64")
erasure-code: Backward compatibility with legacy EC plugins Resurrected jerasure_generic, jerasure_sse3, jerasure_sse4, jerasure_neon, shec_generic, shec_sse3, shec_sse4 and shec_neon. These all are exact copies of the new jerasure and shec plugins that support SIMD detection. Moved EC preload code in ceph-mon and ceph-osd to a central location, added warning when preloading legacy plugins. OSMonitor::get_erasure_code and OSDMonitor:normalize_profile will now check if legacy EC plugins are used and log a warning. Added tests to check that warnings make it to the log. Signed-off-by: Bassam Tabbara <bassam.tabbara@quantum.com>
2016-09-21 14:00:01 +00:00
set(HAVE_ARM 1)
cmake: detect armv8 crc and crypto feature using CHECK_C_COMPILER_FLAG we are using GCC7 and up for C++17 support since mimic, and per https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/AArch64-Options.html , GCC 4.9 and up should be able to support crc and crypto features if these archs are enabled at GCC's configure-time. so we should always use the -march for detecting the compiler's support instead of using the inline assembly now. GCC 4.8 is an ancient compiler, and per https://gcc.gnu.org/gcc-4.8/changes.html, it was the the first GCC release which offers AArch64 support. so we don't need to cater for this GCC version. and we can trust GCC-7 and up. Fixes: http://tracker.ceph.com/issues/17516 Signed-off-by: Kefu Chai <kchai@redhat.com>
2018-09-19 06:17:38 +00:00
include(CheckCCompilerFlag)
cmake/modules/SIMDExt.cmake: armv8 crypto intrinsics Test not only for -march support, but also the actual presence of the intrinsic routines. Not sure why, but gcc 4.8.5 passes the first but not the second. Fixes: http://tracker.ceph.com/issues/19386 Signed-off-by: Dan Mick <dan.mick@redhat.com>
2017-03-25 03:12:38 +00:00
cmake: detect armv8 crc and crypto feature using CHECK_C_COMPILER_FLAG we are using GCC7 and up for C++17 support since mimic, and per https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/AArch64-Options.html , GCC 4.9 and up should be able to support crc and crypto features if these archs are enabled at GCC's configure-time. so we should always use the -march for detecting the compiler's support instead of using the inline assembly now. GCC 4.8 is an ancient compiler, and per https://gcc.gnu.org/gcc-4.8/changes.html, it was the the first GCC release which offers AArch64 support. so we don't need to cater for this GCC version. and we can trust GCC-7 and up. Fixes: http://tracker.ceph.com/issues/17516 Signed-off-by: Kefu Chai <kchai@redhat.com>
2018-09-19 06:17:38 +00:00
check_c_compiler_flag(-march=armv8-a+crc+crypto HAVE_ARMV8_CRC_CRYPTO_INTRINSICS)
crc32c: optimize aarch64 crc32c implementation ARMv8 defines PMULL crypto instruction. This patch optimizes crc32c calculate with the instruction when available rather than original linear crc instructions. ceph crc32c performance unit test shows that the optimization get ~ x3.90 speedups on ThunderX ARM Core@2.0GHz (Cavium) ~ x1.45 speedups on ARM Cortex-A57@2.1GHz (Huaiwei) ~ x1.16 speedups on ARM Cortex-A57@2.0GHz (Softiron) Jira: ENTLLT-358 Change-Id: I657422cd20c9ca78237cd060210a5383f4122575 Signed-off-by: wei xiao <wei.xiao@linaro.org>
2017-01-13 04:36:39 +00:00
if(HAVE_ARMV8_CRC_CRYPTO_INTRINSICS)
cmake: detect armv8 crc and crypto feature using CHECK_C_COMPILER_FLAG we are using GCC7 and up for C++17 support since mimic, and per https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/AArch64-Options.html , GCC 4.9 and up should be able to support crc and crypto features if these archs are enabled at GCC's configure-time. so we should always use the -march for detecting the compiler's support instead of using the inline assembly now. GCC 4.8 is an ancient compiler, and per https://gcc.gnu.org/gcc-4.8/changes.html, it was the the first GCC release which offers AArch64 support. so we don't need to cater for this GCC version. and we can trust GCC-7 and up. Fixes: http://tracker.ceph.com/issues/17516 Signed-off-by: Kefu Chai <kchai@redhat.com>
2018-09-19 06:17:38 +00:00
set(ARMV8_CRC_COMPILE_FLAGS "-march=armv8-a+crc+crypto")
set(HAVE_ARMV8_CRC TRUE)
set(HAVE_ARMV8_CRYPTO TRUE)
else()
check_c_compiler_flag(-march=armv8-a+crc HAVE_ARMV8_CRC)
check_c_compiler_flag(-march=armv8-a+crypto HAVE_ARMV8_CRYPTO)
if(HAVE_ARMV8_CRC)
set(ARMV8_CRC_COMPILE_FLAGS "-march=armv8-a+crc")
elseif(HAVE_ARMV8_CRYPTO)
set(ARMV8_CRC_COMPILE_FLAGS "-march=armv8-a+crypto")
endif()
crc32c: optimize aarch64 crc32c implementation ARMv8 defines PMULL crypto instruction. This patch optimizes crc32c calculate with the instruction when available rather than original linear crc instructions. ceph crc32c performance unit test shows that the optimization get ~ x3.90 speedups on ThunderX ARM Core@2.0GHz (Cavium) ~ x1.45 speedups on ARM Cortex-A57@2.1GHz (Huaiwei) ~ x1.16 speedups on ARM Cortex-A57@2.0GHz (Softiron) Jira: ENTLLT-358 Change-Id: I657422cd20c9ca78237cd060210a5383f4122575 Signed-off-by: wei xiao <wei.xiao@linaro.org>
2017-01-13 04:36:39 +00:00
endif()
cmake/modules/SIMDExt.cmake: add whitespace readability, man, readability Signed-off-by: Dan Mick <dan.mick@redhat.com>
2017-03-25 03:10:15 +00:00
erasure-code: Remove SIMD flavors for jerasure and shec By switching to a new gf-complete with SIMD runtime detection, we can now remove all the different flavors of jerasure and shec. This simplifies deployment and configuration of erasure coding, enables hetergenous OSDs, and enables us to take advantage of new performance improvements in jerasure without config/build changes. This commit removes flavors from cmake, removes ErasureCodePluginSelect___, and fixes unit tests. There is now a single plugin for jerasure and a single plugin for shec. SIMDExt.cmake was changed so that its a little more generic, and is not polluted with gf-complete specific CFLAG defines. The #define for SIMD instruction were based on gf-complete. I also added a small init helper for jerasure that has code that was common between jerasure and shec. Signed-off-by: Bassam Tabbara <bassam.tabbara@quantum.com>
2016-09-22 19:40:52 +00:00
CHECK_C_COMPILER_FLAG(-march=armv8-a+simd HAVE_ARMV8_SIMD)
if(HAVE_ARMV8_SIMD)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -march=armv8-a+simd")
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
endif()
cmake/modules/SIMDExt.cmake: add whitespace readability, man, readability Signed-off-by: Dan Mick <dan.mick@redhat.com>
2017-03-25 03:10:15 +00:00
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "arm|ARM")
crc32c: optimize aarch64 crc32c implementation ARMv8 defines PMULL crypto instruction. This patch optimizes crc32c calculate with the instruction when available rather than original linear crc instructions. ceph crc32c performance unit test shows that the optimization get ~ x3.90 speedups on ThunderX ARM Core@2.0GHz (Cavium) ~ x1.45 speedups on ARM Cortex-A57@2.1GHz (Huaiwei) ~ x1.16 speedups on ARM Cortex-A57@2.0GHz (Softiron) Jira: ENTLLT-358 Change-Id: I657422cd20c9ca78237cd060210a5383f4122575 Signed-off-by: wei xiao <wei.xiao@linaro.org>
2017-01-13 04:36:39 +00:00
set(HAVE_ARM 1)
erasure-code: Remove SIMD flavors for jerasure and shec By switching to a new gf-complete with SIMD runtime detection, we can now remove all the different flavors of jerasure and shec. This simplifies deployment and configuration of erasure coding, enables hetergenous OSDs, and enables us to take advantage of new performance improvements in jerasure without config/build changes. This commit removes flavors from cmake, removes ErasureCodePluginSelect___, and fixes unit tests. There is now a single plugin for jerasure and a single plugin for shec. SIMDExt.cmake was changed so that its a little more generic, and is not polluted with gf-complete specific CFLAG defines. The #define for SIMD instruction were based on gf-complete. I also added a small init helper for jerasure that has code that was common between jerasure and shec. Signed-off-by: Bassam Tabbara <bassam.tabbara@quantum.com>
2016-09-22 19:40:52 +00:00
CHECK_C_COMPILER_FLAG(-mfpu=neon HAVE_ARM_NEON)
if(HAVE_ARM_NEON)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -mfpu=neon")
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
endif()
cmake/modules/SIMDExt.cmake: add whitespace readability, man, readability Signed-off-by: Dan Mick <dan.mick@redhat.com>
2017-03-25 03:10:15 +00:00
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "i386|i686|amd64|x86_64|AMD64")
crc32c: optimize aarch64 crc32c implementation ARMv8 defines PMULL crypto instruction. This patch optimizes crc32c calculate with the instruction when available rather than original linear crc instructions. ceph crc32c performance unit test shows that the optimization get ~ x3.90 speedups on ThunderX ARM Core@2.0GHz (Cavium) ~ x1.45 speedups on ARM Cortex-A57@2.1GHz (Huaiwei) ~ x1.16 speedups on ARM Cortex-A57@2.0GHz (Softiron) Jira: ENTLLT-358 Change-Id: I657422cd20c9ca78237cd060210a5383f4122575 Signed-off-by: wei xiao <wei.xiao@linaro.org>
2017-01-13 04:36:39 +00:00
set(HAVE_INTEL 1)
build: misc fixes for cmake build on i386 Scope SIMD CPU flag detection base on target architecture, resolving build failures in gf-complete on i386; this is inline with the previous autotools based feature detection. Only compile crypto/isa-l if yasm 64 bit complier is found, effectively limiting scope to x86_64. Signed-off-by: James Page <james.page@ubuntu.com>
2017-06-06 14:01:40 +00:00
if(CMAKE_SYSTEM_PROCESSOR MATCHES "i686|amd64|x86_64|AMD64")
CHECK_C_COMPILER_FLAG(-msse HAVE_INTEL_SSE)
if(HAVE_INTEL_SSE)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -msse")
endif()
if(CMAKE_SYSTEM_PROCESSOR MATCHES "amd64|x86_64|AMD64")
CHECK_C_COMPILER_FLAG(-msse2 HAVE_INTEL_SSE2)
if(HAVE_INTEL_SSE2)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -msse2")
endif()
CHECK_C_COMPILER_FLAG(-msse3 HAVE_INTEL_SSE3)
if(HAVE_INTEL_SSE3)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -msse3")
endif()
CHECK_C_COMPILER_FLAG(-mssse3 HAVE_INTEL_SSSE3)
if(HAVE_INTEL_SSSE3)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -mssse3")
endif()
CHECK_C_COMPILER_FLAG(-mpclmul HAVE_INTEL_PCLMUL)
if(HAVE_INTEL_PCLMUL)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -mpclmul")
endif()
CHECK_C_COMPILER_FLAG(-msse4.1 HAVE_INTEL_SSE4_1)
if(HAVE_INTEL_SSE4_1)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -msse4.1")
endif()
CHECK_C_COMPILER_FLAG(-msse4.2 HAVE_INTEL_SSE4_2)
if(HAVE_INTEL_SSE4_2)
set(SIMD_COMPILE_FLAGS "${SIMD_COMPILE_FLAGS} -msse4.2")
endif()
endif(CMAKE_SYSTEM_PROCESSOR MATCHES "amd64|x86_64|AMD64")
endif(CMAKE_SYSTEM_PROCESSOR MATCHES "i686|amd64|x86_64|AMD64")
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "(powerpc|ppc)")
Fix ppc64 support for ceph The ppc64 support requires a couple of changes: - adding the ppc64 support to cmake - changing optimized crc32 code to compile on ppc64le only - moving ifdef condition before crc32_align to avoid defined but not used warning Signed-off-by: Boris Ranto <branto@redhat.com>
2017-07-31 17:50:23 +00:00
if(CMAKE_SYSTEM_PROCESSOR MATCHES "(powerpc|ppc)64le")
set(HAVE_PPC64LE 1)
message(STATUS " we are ppc64le")
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "(powerpc|ppc)64")
Fix ppc64 support for ceph The ppc64 support requires a couple of changes: - adding the ppc64 support to cmake - changing optimized crc32 code to compile on ppc64le only - moving ifdef condition before crc32_align to avoid defined but not used warning Signed-off-by: Boris Ranto <branto@redhat.com>
2017-07-31 17:50:23 +00:00
set(HAVE_PPC64 1)
message(STATUS " we are ppc64")
arch,cmake: compile ppc.c on all powerpc machines * cmake/modules/SIMDExt.cmake: define HAVE_PPC for 32-bit PowerPC. * src/arch/CMakeLists.txt: compile ppc.c for all PowerPC architectures, including powerpc (32-bit PowerPC), ppc64el (64-bit Little Endian PowerPC) and ppc64 (64-bit Big Endian PowerPC). before this change, ppc.c is only compiled if HAVE_POWER8 is defined. but Power8 is a 64-bit PowerPC architecture. while in src/arch/probe.cc, we check for `defined(__powerpc__) || defined(__ppc__)`, if this is true, ceph_arch_ppc_probe() is used to check for the support of Altivec. but on non-power8 PowerPC machines, the linker fails to find the symbols like ceph_arch_ppc_probe(), as ppc.c is not compiled on them. in this change, ppc.c is compiled on all PowerPC architectures, so that ceph_arch_ppc_probe() is also available on non-power8 machines. this change does not impact the behavior of non-power8 machines. because on them, the runtime check would fail to detect the existence of PPC_FEATURE2_VEC_CRYPTO instructions. Reported-by: Mattias Ellert <mattias.ellert@physics.uu.se> Signed-off-by: Kefu Chai <tchaikov@gmail.com>
2021-08-29 14:24:30 +00:00
else()
set(HAVE_PPC 1)
endif()
cmake: extract ppc64le detection into SIMDExt.cmake Signed-off-by: Kefu Chai <kchai@redhat.com>
2017-04-02 17:01:52 +00:00
CHECK_C_COMPILER_FLAG("-maltivec" HAS_ALTIVEC)
if(HAS_ALTIVEC)
message(STATUS " HAS_ALTIVEC yes")
cmake: use add_compile_options() instead of appending compile flags to CMAKE_C_FLAGS, use add_compile_options(), as COMPILE_OPTIONS is a list, it'd simpler to append options to it and to access it in a structured way. Signed-off-by: Kefu Chai <kchai@redhat.com>
2020-06-17 23:08:06 +00:00
add_compile_options(-maltivec)
cmake: extract ppc64le detection into SIMDExt.cmake Signed-off-by: Kefu Chai <kchai@redhat.com>
2017-04-02 17:01:52 +00:00
endif()
CHECK_C_COMPILER_FLAG("-mcpu=power8" HAVE_POWER8)
if(HAVE_POWER8)
message(STATUS " HAVE_POWER8 yes")
endif()
cmake: pass -DINTEL* to gf-complete cflags * in addition to the -march=foobar, we also need to pass -DFOOBAR to gf-complete sources' cflags, so that the SIMD instructions can be generated as expected. * also extract the compiler support for instruction extensions detections into SIMDExt.cmake. * and only check the compiler support if CMAKE_SYSTEM_PROCESSOR matches with the instruction-set/arch to be checked. Signed-off-by: tone.zhang <tone.zhang@linaro.org> Signed-off-by: Kefu Chai <kchai@redhat.com>
2016-09-02 06:38:21 +00:00
endif()