Build ITK for older CPUs

nm97 · December 24, 2019, 7:43am

Hi,

I would like to know what would be the best way to build ITK for different set of CPU instrctions.
I get crash for certain machines that do not have SSE4 or SSE3 CPU instruction.
Is it possible to build multiple dlls corresponding to different set of instructions enabled and control the pick the right dlls from the code?

Any help would be appreciated

Thank you,
Hrach.

blowekamp · December 24, 2019, 12:43pm

Set these CMAKE variables:

github.com

SimpleITK/SimpleITK/blob/master/Testing/CI/Azure/templates/package-mac-job.yml#L49


  env:
    CTEST_BINARY_DIRECTORY: $(coreBinaryDirectory)
    CTEST_OUTPUT_ON_FALURE: 1
    DASHBOARD_BRANCH_DIRECTORY: $(Agent.BuildDirectory)/SimpleITK-dashboard
    ITK_GLOBAL_DEFAULT_NUMBER_OF_THREADS: 2
    CTEST_CACHE: |
      CMAKE_CXX_FLAGS:STRING=-fvisibility=hidden -fvisibility-inlines-hidden
      CMAKE_C_FLAGS:STRING=-fvisibility=hidden
      CMAKE_OSX_DEPLOYMENT_TARGET=10.9
      ITK_C_OPTIMIZATION_FLAGS:STRING=
      ITK_CXX_OPTIMIZATION_FLAGS:STRING=
      BUILD_DOCUMENTS:BOOL=OFF
      BUILD_EXAMPLES:BOOL=OFF
      BUILD_SHARED_LIBS:BOOL=OFF
      BUILD_TESTING:BOOL=ON
      WRAP_DEFAULT:BOOL=OFF
      SimpleITK_BUILD_DISTRIBUTE:BOOL=ON
- bash: |
    set -xe
    if GIT_DIR=${BUILD_SOURCESDIRECTORY}/.git git rev-parse "${DASHBOARD_GIT_BRANCH}^{tag}" >/dev/null 2>&1
    then

nm97 · December 24, 2019, 1:36pm

As I understand by this way I turn off the optimizations.
This will cause slower performance.
Am I right?

dzenanz · December 25, 2019, 4:36pm

You can explore what is done with optimization flags in this file:

github.com

InsightSoftwareConsortium/ITK/blob/master/CMake/ITKSetStandardCompilerFlags.cmake

# trict-null-sentinel Check the set of common warning flags supported by C and C++ compilers
# check_compiler_warning_flags(<c_flags_var> <cxx_flags_var>)
#  <c_flags_var> - variable to store valid C warning flags
#  <cxx_flags_var> - variable to store valid CXX warning flags
# This internally calls the check_c_compiler_flag and check_cxx_compiler_flag macros.


# To create a portable build system, it is best to not
# test for platforms, but to test for features.
#
# Instead of testing "if Windows then do this", test for
# "if the -Wno-invalid-offsetof flag works then use it".
#
# Typical use of this module is:
#
#  include(CheckCompilerWarningFlags)
#  check_compiler_warning_flags(C_WARNING_FLAGS CXX_WARNING_FLAGS)
#  set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} ${C_WARNING_FLAGS}")
#  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${CXX_WARNING_FLAGS}")

This file has been truncated. show original