From c11f71313ad25ed89a1b94ccbbe4023cf857fe4b Mon Sep 17 00:00:00 2001 From: Scott K Logan Date: Tue, 10 Oct 2023 11:25:21 -0500 Subject: [PATCH] Pass -mno-avx512f flag to disable AVX512 opcodes in debs It seems that when we build packages on Xeon systems which support the AVX512 extension, the corresponding opcode is used in the resulting binaries. This leads to SIGILL on platforms which don't support the extension, so we should explicitly disable it to maintain wide compatibility. --- humble/release-build.yaml | 3 +++ iron/release-build.yaml | 3 +++ rolling/release-build.yaml | 3 +++ 3 files changed, 9 insertions(+) diff --git a/humble/release-build.yaml b/humble/release-build.yaml index 9ac6726b..58c0cb60 100644 --- a/humble/release-build.yaml +++ b/humble/release-build.yaml @@ -4,6 +4,9 @@ abi_incompatibility_assumed: true build_environment_variables: + # Disable AVX512 opcodes in case we build on Xeon + DEB_CFLAGS_MAINT_APPEND: -mno-avx512f + DEB_CXXFLAGS_MAINT_APPEND: -mno-avx512f RTI_NC_LICENSE_ACCEPTED: 'yes' jenkins_binary_job_priority: 85 diff --git a/iron/release-build.yaml b/iron/release-build.yaml index e0a2ff82..50b837ea 100644 --- a/iron/release-build.yaml +++ b/iron/release-build.yaml @@ -4,6 +4,9 @@ abi_incompatibility_assumed: true build_environment_variables: + # Disable AVX512 opcodes in case we build on Xeon + DEB_CFLAGS_MAINT_APPEND: -mno-avx512f + DEB_CXXFLAGS_MAINT_APPEND: -mno-avx512f RTI_NC_LICENSE_ACCEPTED: 'yes' jenkins_binary_job_priority: 84 diff --git a/rolling/release-build.yaml b/rolling/release-build.yaml index 36a083be..63e07eb0 100644 --- a/rolling/release-build.yaml +++ b/rolling/release-build.yaml @@ -4,6 +4,9 @@ abi_incompatibility_assumed: true build_environment_variables: + # Disable AVX512 opcodes in case we build on Xeon + DEB_CFLAGS_MAINT_APPEND: -mno-avx512f + DEB_CXXFLAGS_MAINT_APPEND: -mno-avx512f RTI_NC_LICENSE_ACCEPTED: 'yes' jenkins_binary_job_priority: 80