Advanced ConfigurationΒΆ

In addition to the normal options provided by CMake, Umpire uses some additional configuration arguments to control optional features and behavior. Each argument is a boolean option, and can be turned on or off:

-DENABLE_CUDA=Off

Here is a summary of the configuration options, their default value, and meaning:

Variable Default Meaning
ENABLE_CUDA On Enable CUDA support
ENABLE_ROCM Off Enable ROCm support
ENABLE_STATISTICS Off Enable collection of memory statistics
ENABLE_TESTING On Build test executables
ENABLE_BENCHMARKS On Build benchmark programs
ENABLE_LOGGING On Enable Logging within Umpire
ENABLE_SLIC Off Enable SLIC logging
ENABLE_ASSERTS On Enable UMPIRE_ASSERT() within Umpire
ENABLE_TOOLS On Enable tools like replay
ENABLE_DOCS Off Build documentation (requires Sphinx and/or Doxygen)

These arguments are explained in more detail below:

  • ENABLE_CUDA This option enables support for NVIDIA GPUs. If Umpire is built without CUDA or ROCM support, then only the HOST allocator is available for use.
  • ENABLE_ROCM This option enables support for AMD GPUs using the ROCm stack and HCC programming model. If Umpire is built without CUDA or ROCM support, then only the HOST allocator is available for use.
  • ENABLE_STATISTICS This option enables collection of memory statistics. If Umpire is built with this option, the Conduit library will also be built.
  • ENABLE_TESTING This option controls whether or not test executables will be built.
  • ENABLE_BENCHMARKS This option will build the benchmark programs used to test performance.
  • ENABLE_LOGGING This option enables usage of Logging services for Umpire
  • ENABLE_SLIC This option enables usage of logging services provided by SLIC.
  • ENABLE_ASSERTS Enable assert() within Umpire
  • ENABLE_TOOLS Enable development tools for Umpire (replay, etc.)
  • ENABLE_DOCS Build user documentation (with Sphinx) and code documentation (with Doxygen)