[ { "path": ".gitattributes", "content": "# default behavior is to always use unix style line endings\n* text eol=lf\n*.png binary\n*.pdn binary\n*.jpg binary\n*.sln binary\n*.suo binary\n*.vcproj binary\n*.patch binary\n*.dll binary\n*.lib binary\n*.exe binary\n" }, { "path": ".gitignore", "content": "build\nide/vs20??/*.db\nide/vs20??/*.opendb\nide/vs20??/*.user\nide/vs20??/.vs\nide/vs20??/VTune*\nout/\ndocs/\n*.zip\n*.tar\n*.gz\n.vscode\n.DS_STore\n" }, { "path": "CMakeLists.txt", "content": "cmake_minimum_required(VERSION 3.18)\nproject(libmimalloc C CXX)\n\nset(CMAKE_C_STANDARD 11)\nset(CMAKE_CXX_STANDARD 17)\n\noption(MI_SECURE \"Use full security mitigations (like guard pages, allocation randomization, double-free mitigation, and free-list corruption detection)\" OFF)\noption(MI_PADDING \"Enable padding to detect heap block overflow (always on in DEBUG or SECURE mode, or with Valgrind/ASAN)\" OFF)\noption(MI_OVERRIDE \"Override the standard malloc interface (i.e. define entry points for 'malloc', 'free', etc)\" ON)\noption(MI_XMALLOC \"Enable abort() call on memory allocation failure by default\" OFF)\noption(MI_SHOW_ERRORS \"Show error and warning messages by default (only enabled by default in DEBUG mode)\" OFF)\noption(MI_GUARDED \"Build with guard pages behind certain object allocations (implies MI_NO_PADDING=ON)\" OFF)\noption(MI_USE_CXX \"Use the C++ compiler to compile the library (instead of the C compiler)\" OFF)\noption(MI_OPT_ARCH \"Only for optimized builds: turn on architecture specific optimizations (for arm64: '-march=armv8.1-a' (2016))\" OFF)\noption(MI_SEE_ASM \"Generate assembly files\" OFF)\noption(MI_OSX_INTERPOSE \"Use interpose to override standard malloc on macOS\" ON)\noption(MI_OSX_ZONE \"Use malloc zone to override standard malloc on macOS\" ON)\noption(MI_WIN_REDIRECT \"Use redirection module ('mimalloc-redirect') on Windows if compiling mimalloc as a DLL\" ON)\noption(MI_WIN_USE_FIXED_TLS \"Use a fixed TLS slot on Windows to avoid extra tests in the malloc fast path\" OFF)\noption(MI_LOCAL_DYNAMIC_TLS \"Use local-dynamic-tls, a slightly slower but dlopen-compatible thread local storage mechanism (Unix)\" OFF)\noption(MI_LIBC_MUSL \"Enable this when linking with musl libc\" OFF)\n\noption(MI_DEBUG \"Enable assertion checks (enabled by default in a debug build)\" OFF)\noption(MI_DEBUG_INTERNAL \"Enable assertion and internal invariant checks (enabled by default in a debug build)\" OFF)\noption(MI_DEBUG_FULL \"Enable assertion checks and expensive internal heap invariant checking\" OFF)\n\noption(MI_DEBUG_TSAN \"Build with thread sanitizer (needs clang)\" OFF)\noption(MI_DEBUG_UBSAN \"Build with undefined-behavior sanitizer (needs clang++)\" OFF)\noption(MI_TRACK_VALGRIND \"Compile with Valgrind support (adds a small overhead)\" OFF)\noption(MI_TRACK_ASAN \"Compile with address sanitizer support (adds a small overhead)\" OFF)\noption(MI_TRACK_ETW \"Compile with Windows event tracing (ETW) support (adds a small overhead)\" OFF)\n\noption(MI_BUILD_SHARED \"Build shared library\" ON)\noption(MI_BUILD_STATIC \"Build static library\" ON)\noption(MI_BUILD_OBJECT \"Build object library\" ON)\noption(MI_BUILD_TESTS \"Build test executables\" ON)\n\noption(MI_SKIP_COLLECT_ON_EXIT \"Skip collecting memory on program exit\" OFF)\noption(MI_NO_PADDING \"Force no use of padding even in DEBUG mode etc.\" OFF)\noption(MI_INSTALL_TOPLEVEL \"Install directly into $CMAKE_INSTALL_PREFIX instead of PREFIX/lib/mimalloc-version\" OFF)\noption(MI_NO_THP \"Disable transparent huge pages support on Linux/Android for the mimalloc process only\" OFF)\noption(MI_EXTRA_CPPDEFS \"Extra pre-processor definitions (use as `-DMI_EXTRA_CPPDEFS=\\\"opt1=val1;opt2=val2\\\"`)\" \"\")\n\n# negated options for vcpkg features\noption(MI_NO_USE_CXX \"Use plain C compilation (has priority over MI_USE_CXX)\" OFF)\noption(MI_NO_OPT_ARCH \"Do not use architecture specific optimizations (like '-march=armv8.1-a' for example) (has priority over MI_OPT_ARCH)\" OFF)\n\n# deprecated options\noption(MI_WIN_USE_FLS \"Use Fiber local storage on Windows to detect thread termination (deprecated)\" OFF)\noption(MI_CHECK_FULL \"Use full internal invariant checking in DEBUG mode (deprecated, use MI_DEBUG_FULL instead)\" OFF)\noption(MI_USE_LIBATOMIC \"Explicitly link with -latomic (on older systems) (deprecated and detected automatically)\" OFF)\n\ninclude(CheckLinkerFlag) # requires cmake 3.18\ninclude(CheckIncludeFiles)\ninclude(GNUInstallDirs)\ninclude(\"cmake/mimalloc-config-version.cmake\")\n\nset(mi_sources\n src/alloc.c\n src/alloc-aligned.c\n src/alloc-posix.c\n src/arena.c\n src/bitmap.c\n src/heap.c\n src/init.c\n src/libc.c\n src/options.c\n src/os.c\n src/page.c\n src/random.c\n src/segment.c\n src/segment-map.c\n src/stats.c\n src/prim/prim.c)\n\nset(mi_cflags \"\")\nset(mi_cflags_static \"\") # extra flags for a static library build\nset(mi_cflags_dynamic \"\") # extra flags for a shared-object library build\nset(mi_libraries \"\")\n\nif(MI_EXTRA_CPPDEFS)\n set(mi_defines ${MI_EXTRA_CPPDEFS})\nelse()\n set(mi_defines \"\")\nendif()\n\n# pass git revision as a define\nif(EXISTS \"${CMAKE_SOURCE_DIR}/.git/index\")\n find_package(Git)\n if(GIT_FOUND)\n execute_process(COMMAND ${GIT_EXECUTABLE} \"describe\" OUTPUT_VARIABLE mi_git_describe RESULT_VARIABLE mi_git_res ERROR_QUIET OUTPUT_STRIP_TRAILING_WHITESPACE)\n if(mi_git_res EQUAL \"0\")\n list(APPEND mi_defines \"MI_GIT_DESCRIBE=${mi_git_describe}\")\n # add to dependencies so we rebuild if the git head commit changes\n set_property(GLOBAL APPEND PROPERTY CMAKE_CONFIGURE_DEPENDS \"${CMAKE_SOURCE_DIR}/.git/index\")\n endif()\n endif()\nendif()\n\n# -----------------------------------------------------------------------------\n# Convenience: set default build type and compiler depending on the build directory\n# -----------------------------------------------------------------------------\n\nmessage(STATUS \"\")\nif (NOT CMAKE_BUILD_TYPE)\n if (\"${CMAKE_BINARY_DIR}\" MATCHES \".*((D|d)ebug|asan|tsan|ubsan|valgrind)$\")\n message(STATUS \"No build type selected, default to 'Debug'\")\n set(CMAKE_BUILD_TYPE \"Debug\")\n else()\n message(STATUS \"No build type selected, default to 'Release'\")\n set(CMAKE_BUILD_TYPE \"Release\")\n endif()\nendif()\n\nif (CMAKE_GENERATOR MATCHES \"^Visual Studio.*$\")\n message(STATUS \"Note: when building with Visual Studio the build type is specified when building.\")\n message(STATUS \"For example: 'cmake --build . --config=Release\")\nendif()\n\nif(\"${CMAKE_BINARY_DIR}\" MATCHES \".*(S|s)ecure$\")\n message(STATUS \"Default to secure build\")\n set(MI_SECURE \"ON\")\nendif()\n\n\n# Determine architecture\nset(MI_OPT_ARCH_FLAGS \"\")\nset(MI_ARCH \"unknown\")\nif(CMAKE_SYSTEM_PROCESSOR MATCHES \"^(x86|i[3456]86)$\" OR CMAKE_GENERATOR_PLATFORM MATCHES \"^(x86|Win32)$\")\n set(MI_ARCH \"x86\")\nelseif(CMAKE_SYSTEM_PROCESSOR MATCHES \"^(x86_64|x64|amd64|AMD64)$\" OR CMAKE_GENERATOR_PLATFORM STREQUAL \"x64\" OR \"x86_64\" IN_LIST CMAKE_OSX_ARCHITECTURES) # must be before arm64\n set(MI_ARCH \"x64\")\nelseif(CMAKE_SYSTEM_PROCESSOR MATCHES \"^(aarch64|arm64|armv[89].?|ARM64)$\" OR CMAKE_GENERATOR_PLATFORM STREQUAL \"ARM64\" OR \"arm64\" IN_LIST CMAKE_OSX_ARCHITECTURES)\n set(MI_ARCH \"arm64\")\nelseif(CMAKE_SYSTEM_PROCESSOR MATCHES \"^(arm|armv[34567].?|ARM)$\")\n set(MI_ARCH \"arm32\")\nelseif(CMAKE_SYSTEM_PROCESSOR MATCHES \"^(riscv|riscv32|riscv64)$\")\n if(CMAKE_SIZEOF_VOID_P==4)\n set(MI_ARCH \"riscv32\")\n else()\n set(MI_ARCH \"riscv64\")\n endif()\nelse()\n set(MI_ARCH ${CMAKE_SYSTEM_PROCESSOR})\nendif()\nmessage(STATUS \"Architecture: ${MI_ARCH}\") # (${CMAKE_SYSTEM_PROCESSOR}, ${CMAKE_GENERATOR_PLATFORM}, ${CMAKE_GENERATOR})\")\n\n# negative overrides (mainly to support vcpkg features)\nif(MI_NO_USE_CXX)\n set(MI_USE_CXX \"OFF\")\nendif()\nif(MI_NO_OPT_ARCH)\n set(MI_OPT_ARCH \"OFF\")\nelseif(MI_ARCH STREQUAL \"arm64\")\n set(MI_OPT_ARCH \"ON\") # enable armv8.1-a by default on arm64 unless MI_NO_OPT_ARCH is set\nendif()\n\n\n# -----------------------------------------------------------------------------\n# Process options\n# -----------------------------------------------------------------------------\n\nif(CMAKE_C_COMPILER_ID STREQUAL \"Clang\" AND CMAKE_CXX_COMPILER_FRONTEND_VARIANT STREQUAL \"MSVC\")\n set(MI_CLANG_CL \"ON\")\nendif()\n\n# put -Wall early so other warnings can be disabled selectively\nif(CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang\")\n if (MI_CLANG_CL)\n list(APPEND mi_cflags -W)\n else()\n list(APPEND mi_cflags -Wall -Wextra -Wpedantic)\n endif()\nendif()\nif(CMAKE_C_COMPILER_ID MATCHES \"GNU\")\n list(APPEND mi_cflags -Wall -Wextra)\nendif()\nif(CMAKE_C_COMPILER_ID MATCHES \"Intel\")\n list(APPEND mi_cflags -Wall)\nendif()\n\n# force C++ compilation with msvc or clang-cl to use modern C++ atomics\nif(CMAKE_C_COMPILER_ID MATCHES \"MSVC|Intel\" OR MI_CLANG_CL)\n set(MI_USE_CXX \"ON\")\nendif()\n\nif(MI_OVERRIDE)\n message(STATUS \"Override standard malloc (MI_OVERRIDE=ON)\")\n if(APPLE)\n if(MI_OSX_ZONE)\n # use zone's on macOS\n message(STATUS \" Use malloc zone to override malloc (MI_OSX_ZONE=ON)\")\n list(APPEND mi_sources src/prim/osx/alloc-override-zone.c)\n list(APPEND mi_defines MI_OSX_ZONE=1)\n if (NOT MI_OSX_INTERPOSE)\n message(STATUS \" WARNING: zone overriding usually also needs interpose (use -DMI_OSX_INTERPOSE=ON)\")\n endif()\n endif()\n if(MI_OSX_INTERPOSE)\n # use interpose on macOS\n message(STATUS \" Use interpose to override malloc (MI_OSX_INTERPOSE=ON)\")\n list(APPEND mi_defines MI_OSX_INTERPOSE=1)\n if (NOT MI_OSX_ZONE)\n message(STATUS \" WARNING: interpose usually also needs zone overriding (use -DMI_OSX_ZONE=ON)\")\n endif()\n endif()\n if(MI_USE_CXX AND MI_OSX_INTERPOSE)\n message(STATUS \" WARNING: if dynamically overriding malloc/free, it is more reliable to build mimalloc as C code (use -DMI_USE_CXX=OFF)\")\n endif()\n endif()\nendif()\n\nif(WIN32)\n if (NOT MI_WIN_REDIRECT)\n # use a negative define for backward compatibility\n list(APPEND mi_defines MI_WIN_NOREDIRECT=1)\n endif()\nendif()\n\nif(MI_SECURE)\n message(STATUS \"Set full secure build (MI_SECURE=ON)\")\n list(APPEND mi_defines MI_SECURE=4)\nendif()\n\nif(MI_TRACK_VALGRIND)\n CHECK_INCLUDE_FILES(\"valgrind/valgrind.h;valgrind/memcheck.h\" MI_HAS_VALGRINDH)\n if (NOT MI_HAS_VALGRINDH)\n set(MI_TRACK_VALGRIND OFF)\n message(WARNING \"Cannot find the 'valgrind/valgrind.h' and 'valgrind/memcheck.h' -- install valgrind first?\")\n message(STATUS \"Disabling Valgrind support (MI_TRACK_VALGRIND=OFF)\")\n else()\n message(STATUS \"Compile with Valgrind support (MI_TRACK_VALGRIND=ON)\")\n list(APPEND mi_defines MI_TRACK_VALGRIND=1)\n endif()\nendif()\n\nif(MI_TRACK_ASAN)\n if (APPLE AND MI_OVERRIDE)\n set(MI_TRACK_ASAN OFF)\n message(WARNING \"Cannot enable address sanitizer support on macOS if MI_OVERRIDE is ON (MI_TRACK_ASAN=OFF)\")\n endif()\n if (MI_TRACK_VALGRIND)\n set(MI_TRACK_ASAN OFF)\n message(WARNING \"Cannot enable address sanitizer support with also Valgrind support enabled (MI_TRACK_ASAN=OFF)\")\n endif()\n if(MI_TRACK_ASAN)\n CHECK_INCLUDE_FILES(\"sanitizer/asan_interface.h\" MI_HAS_ASANH)\n if (NOT MI_HAS_ASANH)\n set(MI_TRACK_ASAN OFF)\n message(WARNING \"Cannot find the 'sanitizer/asan_interface.h' -- install address sanitizer support first\")\n message(STATUS \"Compile **without** address sanitizer support (MI_TRACK_ASAN=OFF)\")\n else()\n message(STATUS \"Compile with address sanitizer support (MI_TRACK_ASAN=ON)\")\n list(APPEND mi_defines MI_TRACK_ASAN=1)\n list(APPEND mi_cflags -fsanitize=address)\n list(APPEND mi_libraries -fsanitize=address)\n endif()\n endif()\nendif()\n\nif(MI_TRACK_ETW)\n if(NOT WIN32)\n set(MI_TRACK_ETW OFF)\n message(WARNING \"Can only enable ETW support on Windows (MI_TRACK_ETW=OFF)\")\n endif()\n if (MI_TRACK_VALGRIND OR MI_TRACK_ASAN)\n set(MI_TRACK_ETW OFF)\n message(WARNING \"Cannot enable ETW support with also Valgrind or ASAN support enabled (MI_TRACK_ETW=OFF)\")\n endif()\n if(MI_TRACK_ETW)\n message(STATUS \"Compile with Windows event tracing support (MI_TRACK_ETW=ON)\")\n list(APPEND mi_defines MI_TRACK_ETW=1)\n endif()\nendif()\n\nif(MI_GUARDED)\n message(STATUS \"Compile guard pages behind certain object allocations (MI_GUARDED=ON)\")\n list(APPEND mi_defines MI_GUARDED=1)\n if(NOT MI_NO_PADDING)\n message(STATUS \" Disabling padding due to guard pages (MI_NO_PADDING=ON)\")\n set(MI_NO_PADDING ON)\n endif()\nendif()\n\nif(MI_SEE_ASM)\n message(STATUS \"Generate assembly listings (MI_SEE_ASM=ON)\")\n list(APPEND mi_cflags -save-temps)\n if(CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang\")\n message(STATUS \"No GNU Line marker\")\n list(APPEND mi_cflags -Wno-gnu-line-marker)\n endif()\nendif()\n\nif(MI_CHECK_FULL)\n message(STATUS \"The MI_CHECK_FULL option is deprecated, use MI_DEBUG_FULL instead\")\n set(MI_DEBUG_FULL \"ON\")\nendif()\n\nif (MI_SKIP_COLLECT_ON_EXIT)\n message(STATUS \"Skip collecting memory on program exit (MI_SKIP_COLLECT_ON_EXIT=ON)\")\n list(APPEND mi_defines MI_SKIP_COLLECT_ON_EXIT=1)\nendif()\n\nif(MI_DEBUG_FULL)\n message(STATUS \"Set debug level to full assertion and internal invariant checking (MI_DEBUG_FULL=ON, expensive)\")\n list(APPEND mi_defines MI_DEBUG=3) # full invariant checking (mi_assert, mi_assert_internal, and mi_assert_expensive)\nelseif(MI_DEBUG_INTERNAL)\n message(STATUS \"Set debug level to internal assertion and invariant checking (MI_DEBUG_INTERNAL=ON)\")\n list(APPEND mi_defines MI_DEBUG=2) # invariant checking (mi_assert and mi_assert_internal)\nelseif(MI_DEBUG)\n message(STATUS \"Set debug level to assertion checking (MI_DEBUG=ON)\")\n list(APPEND mi_defines MI_DEBUG=1) # assertion checking (mi_assert)\nelseif(CMAKE_BUILD_TYPE MATCHES \"Debug\")\n message(STATUS \"Set debug level to internal assertion and invariant checking (CMAKE_BUILD_TYPE=Debug)\")\n set(MI_DEBUG_INTERNAL ON)\n list(APPEND mi_defines MI_DEBUG=2) # invariant checking (mi_assert and mi_assert_internal)\nendif()\n\nif(MI_NO_PADDING)\n message(STATUS \"Suppress any padding of heap blocks (MI_NO_PADDING=ON)\")\n list(APPEND mi_defines MI_PADDING=0)\nelse()\n if(MI_PADDING)\n message(STATUS \"Enable explicit padding of heap blocks (MI_PADDING=ON)\")\n list(APPEND mi_defines MI_PADDING=1)\n endif()\nendif()\n\nif(MI_XMALLOC)\n message(STATUS \"Enable abort() calls on memory allocation failure (MI_XMALLOC=ON)\")\n list(APPEND mi_defines MI_XMALLOC=1)\nendif()\n\nif(MI_SHOW_ERRORS)\n message(STATUS \"Enable printing of error and warning messages by default (MI_SHOW_ERRORS=ON)\")\n list(APPEND mi_defines MI_SHOW_ERRORS=1)\nendif()\n\nif(MI_DEBUG_TSAN)\n if(CMAKE_C_COMPILER_ID MATCHES \"Clang\")\n message(STATUS \"Build with thread sanitizer (MI_DEBUG_TSAN=ON)\")\n list(APPEND mi_defines MI_TSAN=1)\n list(APPEND mi_cflags -fsanitize=thread -g -O1)\n list(APPEND mi_libraries -fsanitize=thread)\n else()\n message(WARNING \"Can only use thread sanitizer with clang (MI_DEBUG_TSAN=ON but ignored)\")\n endif()\nendif()\n\nif(MI_DEBUG_UBSAN)\n if(CMAKE_BUILD_TYPE MATCHES \"Debug\")\n if(CMAKE_CXX_COMPILER_ID MATCHES \"Clang\")\n message(STATUS \"Build with undefined-behavior sanitizer (MI_DEBUG_UBSAN=ON)\")\n list(APPEND mi_defines MI_UBSAN=1)\n list(APPEND mi_cflags -fsanitize=undefined -g -fno-sanitize-recover=undefined)\n list(APPEND mi_libraries -fsanitize=undefined)\n if (NOT MI_USE_CXX)\n message(STATUS \"(switch to use C++ due to MI_DEBUG_UBSAN)\")\n set(MI_USE_CXX \"ON\")\n endif()\n else()\n message(WARNING \"Can only use undefined-behavior sanitizer with clang++ (MI_DEBUG_UBSAN=ON but ignored)\")\n endif()\n else()\n message(WARNING \"Can only use undefined-behavior sanitizer with a debug build (CMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE})\")\n endif()\nendif()\n\nif(MI_USE_CXX)\n message(STATUS \"Use the C++ compiler to compile (MI_USE_CXX=ON)\")\n set_source_files_properties(${mi_sources} PROPERTIES LANGUAGE CXX )\n set_source_files_properties(src/static.c test/test-api.c test/test-api-fill test/test-stress PROPERTIES LANGUAGE CXX )\n if(CMAKE_CXX_COMPILER_ID MATCHES \"AppleClang|Clang\")\n list(APPEND mi_cflags -Wno-deprecated)\n endif()\n if(CMAKE_CXX_COMPILER_ID MATCHES \"Intel\" AND NOT CMAKE_CXX_COMPILER_ID MATCHES \"IntelLLVM\")\n list(APPEND mi_cflags -Kc++)\n endif()\nendif()\n\nif(CMAKE_SYSTEM_NAME MATCHES \"Linux|Android\")\n if(MI_NO_THP)\n message(STATUS \"Disable transparent huge pages support (MI_NO_THP=ON)\")\n list(APPEND mi_defines MI_NO_THP=1)\n endif()\nendif()\n\nif(MI_LIBC_MUSL)\n message(STATUS \"Assume using musl libc (MI_LIBC_MUSL=ON)\")\n list(APPEND mi_defines MI_LIBC_MUSL=1)\nendif()\n\nif(MI_WIN_USE_FLS)\n message(STATUS \"Use the Fiber API to detect thread termination (deprecated) (MI_WIN_USE_FLS=ON)\")\n list(APPEND mi_defines MI_WIN_USE_FLS=1)\nendif()\n\nif(MI_WIN_USE_FIXED_TLS)\n message(STATUS \"Use fixed TLS slot on Windows to avoid extra tests in the malloc fast path (MI_WIN_USE_FIXED_TLS=ON)\")\n list(APPEND mi_defines MI_WIN_USE_FIXED_TLS=1)\nendif()\n\n# Check /proc/cpuinfo for an SV39 MMU and limit the virtual address bits.\n# (this will skip the aligned hinting in that case. Issue #939, #949)\nif (EXISTS /proc/cpuinfo)\n file(STRINGS /proc/cpuinfo mi_sv39_mmu REGEX \"^mmu[ \\t]+:[ \\t]+sv39$\")\n if (mi_sv39_mmu)\n MESSAGE( STATUS \"Set virtual address bits to 39 (SV39 MMU detected)\" )\n list(APPEND mi_defines MI_DEFAULT_VIRTUAL_ADDRESS_BITS=39)\n endif()\nendif()\n\n# On Haiku use `-DCMAKE_INSTALL_PREFIX` instead, issue #788\n# if(CMAKE_SYSTEM_NAME MATCHES \"Haiku\")\n# SET(CMAKE_INSTALL_LIBDIR ~/config/non-packaged/lib)\n# SET(CMAKE_INSTALL_INCLUDEDIR ~/config/non-packaged/headers)\n# endif()\n\n# Compiler flags\nif(CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang|GNU\" AND NOT MI_CLANG_CL)\n list(APPEND mi_cflags -Wno-unknown-pragmas -fvisibility=hidden)\n if(NOT MI_USE_CXX)\n list(APPEND mi_cflags -Wstrict-prototypes)\n endif()\n if(CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang\")\n list(APPEND mi_cflags -Wno-static-in-inline)\n endif()\nendif()\n\nif(CMAKE_C_COMPILER_ID MATCHES \"Intel\")\n list(APPEND mi_cflags -fvisibility=hidden)\nendif()\n\nif(CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang|GNU|Intel\" AND NOT CMAKE_SYSTEM_NAME MATCHES \"Haiku\" AND NOT MI_CLANG_CL)\n if(MI_LOCAL_DYNAMIC_TLS)\n list(APPEND mi_cflags -ftls-model=local-dynamic)\n else()\n if(MI_LIBC_MUSL)\n # with musl we use local-dynamic for the static build, see issue #644\n list(APPEND mi_cflags_static -ftls-model=local-dynamic)\n list(APPEND mi_cflags_dynamic -ftls-model=initial-exec)\n message(STATUS \"Use local dynamic TLS for the static build (since MI_LIBC_MUSL=ON)\")\n else()\n list(APPEND mi_cflags -ftls-model=initial-exec)\n endif()\n endif()\n if(MI_OVERRIDE)\n list(APPEND mi_cflags -fno-builtin-malloc)\n endif()\nendif()\n\nif(CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang|GNU|Intel\" AND NOT CMAKE_SYSTEM_NAME MATCHES \"Haiku\")\n if(MI_OPT_ARCH)\n if(APPLE AND CMAKE_C_COMPILER_ID MATCHES \"AppleClang|Clang\" AND CMAKE_OSX_ARCHITECTURES) # to support multi-arch binaries (#999)\n if(\"arm64\" IN_LIST CMAKE_OSX_ARCHITECTURES)\n list(APPEND MI_OPT_ARCH_FLAGS \"-Xarch_arm64;-march=armv8.1-a\")\n endif()\n elseif(MI_ARCH STREQUAL \"arm64\")\n set(MI_OPT_ARCH_FLAGS \"-march=armv8.1-a\") # fast atomics\n endif()\n endif()\nendif()\n\nif (MSVC AND MSVC_VERSION GREATER_EQUAL 1914)\n list(APPEND mi_cflags /Zc:__cplusplus)\n if(MI_OPT_ARCH AND NOT MI_CLANG_CL)\n if(MI_ARCH STREQUAL \"arm64\")\n set(MI_OPT_ARCH_FLAGS \"/arch:armv8.1\") # fast atomics\n endif()\n endif()\nendif()\n\nif(MINGW)\n add_definitions(-D_WIN32_WINNT=0x600) # issue #976\nendif()\n\nif(MI_OPT_ARCH_FLAGS)\n list(APPEND mi_cflags ${MI_OPT_ARCH_FLAGS})\n message(STATUS \"Architecture specific optimization is enabled (with ${MI_OPT_ARCH_FLAGS}) (MI_OPT_ARCH=ON)\")\nendif()\n\n# extra needed libraries\n\n# we prefer -l test over `find_library` as sometimes core libraries\n# like `libatomic` are not on the system path (see issue #898)\nfunction(find_link_library libname outlibname)\n check_linker_flag(C \"-l${libname}\" mi_has_lib${libname})\n if (mi_has_lib${libname})\n message(VERBOSE \"link library: -l${libname}\")\n set(${outlibname} ${libname} PARENT_SCOPE)\n else()\n find_library(MI_LIBPATH_${libname} ${libname})\n if (MI_LIBPATH_${libname})\n message(VERBOSE \"link library ${libname} at ${MI_LIBPATH_${libname}}\")\n set(${outlibname} ${MI_LIBPATH_${libname}} PARENT_SCOPE)\n else()\n message(VERBOSE \"link library not found: ${libname}\")\n set(${outlibname} \"\" PARENT_SCOPE)\n endif()\n endif()\nendfunction()\n\nif(WIN32)\n list(APPEND mi_libraries psapi shell32 user32 advapi32 bcrypt)\nelse()\n find_link_library(\"pthread\" MI_LIB_PTHREAD)\n if(MI_LIB_PTHREAD)\n list(APPEND mi_libraries \"${MI_LIB_PTHREAD}\")\n endif()\n find_link_library(\"rt\" MI_LIB_RT)\n if(MI_LIB_RT)\n list(APPEND mi_libraries \"${MI_LIB_RT}\")\n endif()\n find_link_library(\"atomic\" MI_LIB_ATOMIC)\n if(MI_LIB_ATOMIC)\n list(APPEND mi_libraries \"${MI_LIB_ATOMIC}\")\n endif()\nendif()\n\n\n# -----------------------------------------------------------------------------\n# Install and output names\n# -----------------------------------------------------------------------------\n\n# dynamic/shared library and symlinks always go to /usr/local/lib equivalent\n# we use ${CMAKE_INSTALL_BINDIR} and ${CMAKE_INSTALL_LIBDIR}.\n\n# static libraries and object files, includes, and cmake config files\n# are either installed at top level, or use versioned directories for side-by-side installation (default)\nif (MI_INSTALL_TOPLEVEL)\n set(mi_install_objdir \"${CMAKE_INSTALL_LIBDIR}\")\n set(mi_install_incdir \"${CMAKE_INSTALL_INCLUDEDIR}\")\n set(mi_install_cmakedir \"${CMAKE_INSTALL_LIBDIR}/cmake/mimalloc\")\nelse()\n set(mi_install_objdir \"${CMAKE_INSTALL_LIBDIR}/mimalloc-${mi_version}\") # for static library and object files\n set(mi_install_incdir \"${CMAKE_INSTALL_INCLUDEDIR}/mimalloc-${mi_version}\") # for includes\n set(mi_install_cmakedir \"${CMAKE_INSTALL_LIBDIR}/cmake/mimalloc-${mi_version}\") # for cmake package info\nendif()\n\nset(mi_libname \"mimalloc\")\nif(MI_SECURE)\n set(mi_libname \"${mi_libname}-secure\")\nendif()\nif(MI_TRACK_VALGRIND)\n set(mi_libname \"${mi_libname}-valgrind\")\nendif()\nif(MI_TRACK_ASAN)\n set(mi_libname \"${mi_libname}-asan\")\nendif()\nstring(TOLOWER \"${CMAKE_BUILD_TYPE}\" CMAKE_BUILD_TYPE_LC)\nlist(APPEND mi_defines \"MI_CMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE_LC}\") #todo: multi-config project needs $ ?\nif(CMAKE_BUILD_TYPE_LC MATCHES \"^(release|relwithdebinfo|minsizerel|none)$\")\n list(APPEND mi_defines MI_BUILD_RELEASE)\nelse()\n set(mi_libname \"${mi_libname}-${CMAKE_BUILD_TYPE_LC}\") #append build type (e.g. -debug) if not a release version\nendif()\n\nif(MI_BUILD_SHARED)\n list(APPEND mi_build_targets \"shared\")\nendif()\nif(MI_BUILD_STATIC)\n list(APPEND mi_build_targets \"static\")\nendif()\nif(MI_BUILD_OBJECT)\n list(APPEND mi_build_targets \"object\")\nendif()\nif(MI_BUILD_TESTS)\n list(APPEND mi_build_targets \"tests\")\nendif()\n\nmessage(STATUS \"\")\nmessage(STATUS \"Library name : ${mi_libname}\")\nmessage(STATUS \"Version : ${mi_version}.${mi_version_patch}\")\nmessage(STATUS \"Build type : ${CMAKE_BUILD_TYPE_LC}\")\nif(MI_USE_CXX)\n message(STATUS \"C++ Compiler : ${CMAKE_CXX_COMPILER}\")\nelse()\n message(STATUS \"C Compiler : ${CMAKE_C_COMPILER}\")\nendif()\nmessage(STATUS \"Compiler flags : ${mi_cflags}\")\nmessage(STATUS \"Compiler defines : ${mi_defines}\")\nmessage(STATUS \"Link libraries : ${mi_libraries}\")\nmessage(STATUS \"Build targets : ${mi_build_targets}\")\nmessage(STATUS \"\")\n\n# -----------------------------------------------------------------------------\n# Main targets\n# -----------------------------------------------------------------------------\n\n# shared library\nif(MI_BUILD_SHARED)\n add_library(mimalloc SHARED ${mi_sources})\n set_target_properties(mimalloc PROPERTIES VERSION ${mi_version} SOVERSION ${mi_version_major} OUTPUT_NAME ${mi_libname} )\n target_compile_definitions(mimalloc PRIVATE ${mi_defines} MI_SHARED_LIB MI_SHARED_LIB_EXPORT)\n target_compile_options(mimalloc PRIVATE ${mi_cflags} ${mi_cflags_dynamic})\n target_link_libraries(mimalloc PRIVATE ${mi_libraries})\n target_include_directories(mimalloc PUBLIC\n $\n $\n )\n install(TARGETS mimalloc EXPORT mimalloc ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR} RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR} LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR})\n install(EXPORT mimalloc DESTINATION ${mi_install_cmakedir})\n\n if(WIN32 AND NOT MINGW)\n # On windows, the import library name for the dll would clash with the static mimalloc.lib library\n # so we postfix the dll import library with `.dll.lib` (and also the .pdb debug file)\n set_property(TARGET mimalloc PROPERTY ARCHIVE_OUTPUT_NAME \"${mi_libname}.dll\" )\n install(FILES \"$/${mi_libname}.dll.lib\" DESTINATION ${CMAKE_INSTALL_LIBDIR})\n set_property(TARGET mimalloc PROPERTY PDB_NAME \"${mi_libname}.dll\")\n # don't try to install the pdb since it may not be generated depending on the configuration\n # install(FILES \"$/${mi_libname}.dll.pdb\" DESTINATION ${CMAKE_INSTALL_LIBDIR})\n endif()\n if(WIN32 AND MI_WIN_REDIRECT)\n if(MINGW)\n set_property(TARGET mimalloc PROPERTY PREFIX \"\")\n endif()\n # On windows, link and copy the mimalloc redirection dll too.\n if(CMAKE_GENERATOR_PLATFORM STREQUAL \"arm64ec\")\n set(MIMALLOC_REDIRECT_SUFFIX \"-arm64ec\")\n elseif(MI_ARCH STREQUAL \"x64\")\n set(MIMALLOC_REDIRECT_SUFFIX \"\")\n if(CMAKE_SYSTEM_PROCESSOR STREQUAL \"ARM64\")\n message(STATUS \"Note: x64 code emulated on Windows for arm64 should use an arm64ec build of 'mimalloc.dll'\")\n message(STATUS \" together with 'mimalloc-redirect-arm64ec.dll'. See the 'bin\\\\readme.md' for more information.\")\n endif()\n elseif(MI_ARCH STREQUAL \"x86\")\n set(MIMALLOC_REDIRECT_SUFFIX \"32\")\n else()\n set(MIMALLOC_REDIRECT_SUFFIX \"-${MI_ARCH}\") # -arm64 etc.\n endif()\n\n target_link_libraries(mimalloc PRIVATE ${CMAKE_CURRENT_SOURCE_DIR}/bin/mimalloc-redirect${MIMALLOC_REDIRECT_SUFFIX}.lib) # the DLL import library\n add_custom_command(TARGET mimalloc POST_BUILD\n COMMAND \"${CMAKE_COMMAND}\" -E copy \"${CMAKE_CURRENT_SOURCE_DIR}/bin/mimalloc-redirect${MIMALLOC_REDIRECT_SUFFIX}.dll\" $\n COMMENT \"Copy mimalloc-redirect${MIMALLOC_REDIRECT_SUFFIX}.dll to output directory\")\n install(FILES \"$/mimalloc-redirect${MIMALLOC_REDIRECT_SUFFIX}.dll\" DESTINATION ${CMAKE_INSTALL_BINDIR})\n endif()\nendif()\n\n\n# static library\nif (MI_BUILD_STATIC)\n add_library(mimalloc-static STATIC ${mi_sources})\n set_property(TARGET mimalloc-static PROPERTY OUTPUT_NAME ${mi_libname})\n set_property(TARGET mimalloc-static PROPERTY POSITION_INDEPENDENT_CODE ON)\n target_compile_definitions(mimalloc-static PRIVATE ${mi_defines} MI_STATIC_LIB)\n target_compile_options(mimalloc-static PRIVATE ${mi_cflags} ${mi_cflags_static})\n target_link_libraries(mimalloc-static PRIVATE ${mi_libraries})\n target_include_directories(mimalloc-static PUBLIC\n $\n $\n )\n install(TARGETS mimalloc-static EXPORT mimalloc DESTINATION ${mi_install_objdir} LIBRARY)\n install(EXPORT mimalloc DESTINATION ${mi_install_cmakedir})\nendif()\n\n# install include files\ninstall(FILES include/mimalloc.h DESTINATION ${mi_install_incdir})\ninstall(FILES include/mimalloc-override.h DESTINATION ${mi_install_incdir})\ninstall(FILES include/mimalloc-new-delete.h DESTINATION ${mi_install_incdir})\ninstall(FILES include/mimalloc-stats.h DESTINATION ${mi_install_incdir})\ninstall(FILES cmake/mimalloc-config.cmake DESTINATION ${mi_install_cmakedir})\ninstall(FILES cmake/mimalloc-config-version.cmake DESTINATION ${mi_install_cmakedir})\n\n\n# single object file for more predictable static overriding\nif (MI_BUILD_OBJECT)\n add_library(mimalloc-obj OBJECT src/static.c)\n set_property(TARGET mimalloc-obj PROPERTY POSITION_INDEPENDENT_CODE ON)\n target_compile_definitions(mimalloc-obj PRIVATE ${mi_defines})\n target_compile_options(mimalloc-obj PRIVATE ${mi_cflags} ${mi_cflags_static})\n target_include_directories(mimalloc-obj PUBLIC\n $\n $\n )\n\n # Copy the generated object file (`static.o`) to the output directory (as `mimalloc.o`)\n if(CMAKE_GENERATOR MATCHES \"^Visual Studio.*$\")\n set(mimalloc-obj-static \"${CMAKE_CURRENT_BINARY_DIR}/mimalloc-obj.dir/$/static${CMAKE_C_OUTPUT_EXTENSION}\")\n else()\n set(mimalloc-obj-static \"${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/mimalloc-obj.dir/src/static.c${CMAKE_C_OUTPUT_EXTENSION}\")\n endif()\n set(mimalloc-obj-out \"${CMAKE_CURRENT_BINARY_DIR}/${mi_libname}${CMAKE_C_OUTPUT_EXTENSION}\")\n add_custom_command(OUTPUT ${mimalloc-obj-out} DEPENDS mimalloc-obj COMMAND \"${CMAKE_COMMAND}\" -E copy \"${mimalloc-obj-static}\" \"${mimalloc-obj-out}\")\n add_custom_target(mimalloc-obj-target ALL DEPENDS ${mimalloc-obj-out})\n\n\n # the following seems to lead to cmake warnings/errors on some systems, disable for now :-(\n # install(TARGETS mimalloc-obj EXPORT mimalloc DESTINATION ${mi_install_objdir})\n\n # the FILES expression can also be: $\n # but that fails cmake versions less than 3.10 so we leave it as is for now\n install(FILES ${mimalloc-obj-static}\n DESTINATION ${mi_install_objdir}\n RENAME ${mi_libname}${CMAKE_C_OUTPUT_EXTENSION} )\nendif()\n\n\n# pkg-config file support\nset(mi_pc_libraries \"\")\nforeach(item IN LISTS mi_libraries)\n if(item MATCHES \" *[-].*\")\n set(mi_pc_libraries \"${mi_pc_libraries} ${item}\")\n else()\n set(mi_pc_libraries \"${mi_pc_libraries} -l${item}\")\n endif()\nendforeach()\n\ninclude(\"cmake/JoinPaths.cmake\")\njoin_paths(mi_pc_includedir \"\\${prefix}\" \"${CMAKE_INSTALL_INCLUDEDIR}\")\njoin_paths(mi_pc_libdir \"\\${prefix}\" \"${CMAKE_INSTALL_LIBDIR}\")\n\nconfigure_file(mimalloc.pc.in mimalloc.pc @ONLY)\ninstall(FILES \"${CMAKE_CURRENT_BINARY_DIR}/mimalloc.pc\"\n DESTINATION \"${CMAKE_INSTALL_LIBDIR}/pkgconfig/\")\n\n\n\n# -----------------------------------------------------------------------------\n# API surface testing\n# -----------------------------------------------------------------------------\n\nif (MI_BUILD_TESTS)\n enable_testing()\n\n # static link tests\n foreach(TEST_NAME api api-fill stress)\n add_executable(mimalloc-test-${TEST_NAME} test/test-${TEST_NAME}.c)\n target_compile_definitions(mimalloc-test-${TEST_NAME} PRIVATE ${mi_defines})\n target_compile_options(mimalloc-test-${TEST_NAME} PRIVATE ${mi_cflags})\n target_include_directories(mimalloc-test-${TEST_NAME} PRIVATE include)\n if(MI_BUILD_STATIC AND NOT MI_DEBUG_TSAN)\n target_link_libraries(mimalloc-test-${TEST_NAME} PRIVATE mimalloc-static ${mi_libraries})\n elseif(MI_BUILD_SHARED)\n target_link_libraries(mimalloc-test-${TEST_NAME} PRIVATE mimalloc ${mi_libraries})\n else()\n message(STATUS \"cannot build TSAN tests without MI_BUILD_SHARED being enabled\")\n endif()\n add_test(NAME test-${TEST_NAME} COMMAND mimalloc-test-${TEST_NAME})\n endforeach()\n\n # dynamic override test\n if(MI_BUILD_SHARED AND NOT (MI_TRACK_ASAN OR MI_DEBUG_TSAN OR MI_DEBUG_UBSAN))\n add_executable(mimalloc-test-stress-dynamic test/test-stress.c)\n target_compile_definitions(mimalloc-test-stress-dynamic PRIVATE ${mi_defines} \"USE_STD_MALLOC=1\")\n target_compile_options(mimalloc-test-stress-dynamic PRIVATE ${mi_cflags})\n target_include_directories(mimalloc-test-stress-dynamic PRIVATE include)\n if(WIN32)\n target_compile_definitions(mimalloc-test-stress-dynamic PRIVATE \"MI_LINK_VERSION=1\") # link mi_version\n target_link_libraries(mimalloc-test-stress-dynamic PRIVATE mimalloc ${mi_libraries}) # link mi_version\n add_test(NAME test-stress-dynamic COMMAND ${CMAKE_COMMAND} -E env MIMALLOC_VERBOSE=1 $)\n else()\n target_link_libraries(mimalloc-test-stress-dynamic PRIVATE ${mi_libraries}) # pthreads, issue 1158\n if(APPLE)\n set(LD_PRELOAD \"DYLD_INSERT_LIBRARIES\")\n else()\n set(LD_PRELOAD \"LD_PRELOAD\")\n endif()\n add_test(NAME test-stress-dynamic COMMAND ${CMAKE_COMMAND} -E env MIMALLOC_VERBOSE=1 ${LD_PRELOAD}=$ $)\n endif()\n endif()\nendif()\n\n# -----------------------------------------------------------------------------\n# Set override properties\n# -----------------------------------------------------------------------------\nif (MI_OVERRIDE)\n if (MI_BUILD_SHARED)\n target_compile_definitions(mimalloc PRIVATE MI_MALLOC_OVERRIDE)\n endif()\n if(NOT WIN32)\n # It is only possible to override malloc on Windows when building as a DLL.\n if (MI_BUILD_STATIC)\n target_compile_definitions(mimalloc-static PRIVATE MI_MALLOC_OVERRIDE)\n endif()\n if (MI_BUILD_OBJECT)\n target_compile_definitions(mimalloc-obj PRIVATE MI_MALLOC_OVERRIDE)\n endif()\n endif()\nendif()\n" }, { "path": "LICENSE", "content": "MIT License\n\nCopyright (c) 2018-2025 Microsoft Corporation, Daan Leijen\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n" }, { "path": "SECURITY.md", "content": "\n\n## Security\n\nMicrosoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet) and [Xamarin](https://github.com/xamarin).\n\nIf you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/security.md/definition), please report it to us as described below.\n\n## Reporting Security Issues\n\n**Please do not report security vulnerabilities through public GitHub issues.**\n\nInstead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/security.md/msrc/create-report).\n\nIf you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/security.md/msrc/pgp).\n\nYou should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc). \n\nPlease include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:\n\n * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)\n * Full paths of source file(s) related to the manifestation of the issue\n * The location of the affected source code (tag/branch/commit or direct URL)\n * Any special configuration required to reproduce the issue\n * Step-by-step instructions to reproduce the issue\n * Proof-of-concept or exploit code (if possible)\n * Impact of the issue, including how an attacker might exploit the issue\n\nThis information will help us triage your report more quickly.\n\nIf you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/security.md/msrc/bounty) page for more details about our active programs.\n\n## Preferred Languages\n\nWe prefer all communications to be in English.\n\n## Policy\n\nMicrosoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/security.md/cvd).\n\n\n" }, { "path": "azure-pipelines.yml", "content": "# Starter pipeline\n# Start with a minimal pipeline that you can customize to build and deploy your code.\n# Add steps that build, run tests, deploy, and more:\n# https://aka.ms/yaml\n\ntrigger:\n branches:\n include:\n - main\n - dev*\n tags:\n include:\n - v*\n\njobs:\n- job:\n displayName: Windows 2022\n pool:\n vmImage:\n windows-2022\n strategy:\n matrix:\n Debug:\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n MSBuildConfiguration: Debug\n Release:\n BuildType: release\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release\n MSBuildConfiguration: Release\n Secure:\n BuildType: secure\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release -DMI_SECURE=ON\n MSBuildConfiguration: Release\n Debug x86:\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -A Win32\n MSBuildConfiguration: Debug\n Release x86:\n BuildType: release\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release -A Win32\n MSBuildConfiguration: Release\n Debug Fixed TLS:\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_WIN_USE_FIXED_TLS=ON\n MSBuildConfiguration: Debug\n Release Fixed TLS:\n BuildType: release\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release -DMI_WIN_USE_FIXED_TLS=ON\n MSBuildConfiguration: Release\n steps:\n - task: CMake@1\n inputs:\n workingDirectory: $(BuildType)\n cmakeArgs: .. $(cmakeExtraArgs)\n - task: MSBuild@1\n inputs:\n solution: $(BuildType)/libmimalloc.sln\n configuration: '$(MSBuildConfiguration)'\n msbuildArguments: -m\n - script: ctest --verbose --timeout 240 -C $(MSBuildConfiguration)\n workingDirectory: $(BuildType)\n displayName: CTest\n #- script: $(BuildType)\\$(BuildType)\\mimalloc-test-stress\n # displayName: TestStress\n #- upload: $(Build.SourcesDirectory)/$(BuildType)\n # artifact: mimalloc-windows-$(BuildType)\n\n- job:\n displayName: Ubuntu 22.04\n pool:\n vmImage:\n ubuntu-22.04\n strategy:\n matrix:\n Debug:\n CC: gcc\n CXX: g++\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n Release:\n CC: gcc\n CXX: g++\n BuildType: release\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release\n Secure:\n CC: gcc\n CXX: g++\n BuildType: secure\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release -DMI_SECURE=ON\n Debug++:\n CC: gcc\n CXX: g++\n BuildType: debug-cxx\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_USE_CXX=ON\n Debug Clang:\n CC: clang\n CXX: clang++\n BuildType: debug-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n Release Clang:\n CC: clang\n CXX: clang++\n BuildType: release-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release\n Secure Clang:\n CC: clang\n CXX: clang++\n BuildType: secure-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release -DMI_SECURE=ON\n Debug++ Clang:\n CC: clang\n CXX: clang++\n BuildType: debug-clang-cxx\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_USE_CXX=ON\n Debug ASAN Clang:\n CC: clang\n CXX: clang++\n BuildType: debug-asan-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_TRACK_ASAN=ON\n Debug UBSAN Clang:\n CC: clang\n CXX: clang++\n BuildType: debug-ubsan-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_DEBUG_UBSAN=ON\n Debug TSAN Clang++:\n CC: clang\n CXX: clang++\n BuildType: debug-tsan-clang-cxx\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=RelWithDebInfo -DMI_USE_CXX=ON -DMI_DEBUG_TSAN=ON\n Debug Guarded Clang:\n CC: clang\n CXX: clang\n BuildType: debug-guarded-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=RelWithDebInfo -DMI_DEBUG_FULL=ON -DMI_GUARDED=ON\n\n steps:\n - task: CMake@1\n inputs:\n workingDirectory: $(BuildType)\n cmakeArgs: .. $(cmakeExtraArgs)\n - script: make -j$(nproc) -C $(BuildType)\n displayName: Make\n - script: ctest --verbose --timeout 240\n workingDirectory: $(BuildType)\n displayName: CTest\n env:\n MIMALLOC_GUARDED_SAMPLE_RATE: 1000\n# - upload: $(Build.SourcesDirectory)/$(BuildType)\n# artifact: mimalloc-ubuntu-$(BuildType)\n\n- job:\n displayName: macOS 14 (Sonoma)\n pool:\n vmImage:\n macOS-14\n strategy:\n matrix:\n Debug:\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n Release:\n BuildType: release\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release\n Secure:\n BuildType: secure\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release -DMI_SECURE=ON\n steps:\n - task: CMake@1\n inputs:\n workingDirectory: $(BuildType)\n cmakeArgs: .. $(cmakeExtraArgs)\n - script: make -j$(sysctl -n hw.ncpu) -C $(BuildType)\n displayName: Make\n - script: ctest --verbose --timeout 240\n workingDirectory: $(BuildType)\n displayName: CTest\n \n# - upload: $(Build.SourcesDirectory)/$(BuildType)\n# artifact: mimalloc-macos-$(BuildType)\n\n# ----------------------------------------------------------\n# Other OS versions (just debug mode)\n# ----------------------------------------------------------\n\n- job:\n displayName: Ubuntu 24.04\n pool:\n vmImage:\n ubuntu-24.04\n strategy:\n matrix:\n Debug:\n CC: gcc\n CXX: g++\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n Debug++:\n CC: gcc\n CXX: g++\n BuildType: debug-cxx\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_USE_CXX=ON\n Debug Clang:\n CC: clang\n CXX: clang++\n BuildType: debug-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n Debug++ Clang:\n CC: clang\n CXX: clang++\n BuildType: debug-clang-cxx\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON -DMI_USE_CXX=ON\n Release Clang:\n CC: clang\n CXX: clang++\n BuildType: release-clang\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release\n steps:\n - task: CMake@1\n inputs:\n workingDirectory: $(BuildType)\n cmakeArgs: .. $(cmakeExtraArgs)\n - script: make -j$(nproc) -C $(BuildType)\n displayName: Make\n - script: ctest --verbose --timeout 240\n workingDirectory: $(BuildType)\n displayName: CTest\n\n- job:\n displayName: macOS 15 (Sequoia)\n pool:\n vmImage:\n macOS-15\n strategy:\n matrix:\n Debug:\n BuildType: debug\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Debug -DMI_DEBUG_FULL=ON\n Release:\n BuildType: release\n cmakeExtraArgs: -DCMAKE_BUILD_TYPE=Release\n steps:\n - task: CMake@1\n inputs:\n workingDirectory: $(BuildType)\n cmakeArgs: .. $(cmakeExtraArgs)\n - script: make -j$(sysctl -n hw.ncpu) -C $(BuildType)\n displayName: Make\n - script: ctest --verbose --timeout 240\n workingDirectory: $(BuildType)\n displayName: CTest\n" }, { "path": "bin/readme.md", "content": "# Windows Override\n\nWe use a separate redirection DLL to override mimalloc on Windows \nsuch that we redirect all malloc/free calls that go through the (dynamic) C runtime allocator, \nincluding those from other DLL's or libraries. As it intercepts all allocation calls on a low level, \nit can be used on large programs that include other 3rd party components.\nThere are four requirements to make the overriding work well:\n\n1. Use the C-runtime library as a DLL (using the `/MD` or `/MDd` switch).\n\n2. Link your program explicitly with the `mimalloc.dll.lib` export library for\n the `mimalloc.dll` -- which contains all mimalloc functionality.\n To ensure the `mimalloc.dll` is actually loaded at run-time it is easiest \n to insert some call to the mimalloc API in the `main` function, like `mi_version()`\n (or use the `/include:mi_version` switch on the linker, or\n similarly, `#pragma comment(linker, \"/include:mi_version\")` in some source file). \n See the `mimalloc-test-override` project for an example on how to use this. \n\n3. The `mimalloc-redirect.dll` must be put in the same folder as the main \n `mimalloc.dll` at runtime (as it is a dependency of that DLL).\n The redirection DLL ensures that all calls to the C runtime malloc API get \n redirected to mimalloc functions (which reside in `mimalloc.dll`).\n\n4. Ensure the `mimalloc.dll` comes as early as possible in the import\n list of the final executable (so it can intercept all potential allocations).\n You can use `minject -l ` to check this if needed.\n\n```csharp\n┌──────────────┐ \n│ Your Program │ \n└────┬─────────┘ \n │ \n │ mi_version() ┌───────────────┐ ┌───────────────────────┐\n ├──────────────►│ mimalloc.dll ├────►│ mimalloc-redirect.dll │\n │ └──────┬────────┘ └───────────────────────┘\n │ ▼ \n │ malloc() etc. ┌──────────────┐ \n ├──────────────►│ ucrtbase.dll │ \n │ └──────────────┘ \n │ \n │ \n └──────────────► ... \n```\n\nFor best performance on Windows with C++, it\nis also recommended to also override the `new`/`delete` operations (by including\n[`mimalloc-new-delete.h`](../include/mimalloc-new-delete.h) \na single(!) source file in your project).\n\nThe environment variable `MIMALLOC_DISABLE_REDIRECT=1` can be used to disable dynamic\noverriding at run-time. Use `MIMALLOC_VERBOSE=1` to check if mimalloc was successfully \nredirected.\n\n### Other Platforms\n\nYou always link with `mimalloc.dll` but for different platforms you may \nneed a specific redirection DLL:\n\n- __x64__: `mimalloc-redirect.dll`.\n- __x86__: `mimalloc-redirect32.dll`. Use for older 32-bit Windows programs.\n- __arm64__: `mimalloc-redirect-arm64.dll`. Use for native Windows arm64 programs.\n- __arm64ec__: `mimalloc-redirect-arm64ec.dll`. The [arm64ec] ABI is \"emulation compatible\" \n mode on Windows arm64. Unfortunately we cannot run x64 code emulated on Windows arm64 with\n the x64 mimalloc override directly (since the C runtime always uses `arm64ec`). Instead:\n 1. Build the program as normal for x64 and link as normal with the x64 \n `mimalloc.lib` export library.\n 2. Now separately build `mimalloc.dll` in `arm64ec` mode and _overwrite_ your\n previous (x64) `mimalloc.dll` -- the loader can handle the mix of arm64ec\n and x64 code. Now use `mimalloc-redirect-arm64ec.dll` to match your new\n arm64ec `mimalloc.dll`. The main program stays as is and can be fully x64 \n or contain more arm64ec modules. At runtime, the arm64ec `mimalloc.dll` will\n run with native arm64 instructions while the rest of the program runs emulated x64.\n\n[arm64ec]: https://learn.microsoft.com/en-us/windows/arm/arm64ec\n\n\n### Minject\n\nWe cannot always re-link an executable with `mimalloc.dll`, and similarly, we \ncannot always ensure that the DLL comes first in the import table of the final executable.\nIn many cases though we can patch existing executables without any recompilation\nif they are linked with the dynamic C runtime (`ucrtbase.dll`) -- just put the \n`mimalloc.dll` into the import table (and put `mimalloc-redirect.dll` in the same \ndirectory) Such patching can be done for example with [CFF Explorer](https://ntcore.com/?page_id=388).\n\nThe `minject` program can also do this from the command line\nUse `minject --help` for options:\n\n```\n> minject --help\n\nminject:\n Injects the mimalloc dll into the import table of a 64-bit executable,\n and/or ensures that it comes first in het import table.\n\nusage:\n > minject [options] \n\noptions:\n -h --help show this help\n -v --verbose be verbose\n -l --list only list imported modules\n -i --inplace update the exe in-place (make sure there is a backup!)\n -f --force always overwrite without prompting\n --postfix=

use

as a postfix to the mimalloc dll.\n e.g. use --postfix=debug to link with mimalloc-debug.dll\n\nnotes:\n Without '--inplace' an injected is generated with the same name ending in '-mi'.\n Ensure 'mimalloc-redirect.dll' is in the same folder as the mimalloc dll.\n\nexamples:\n > minject --list myprogram.exe\n > minject --force --inplace myprogram.exe\n``` \n\nFor x86 32-bit binaries, use `minject32`, and for arm64 binaries use `minject-arm64`.\n\n" }, { "path": "cmake/JoinPaths.cmake", "content": "# This module provides function for joining paths\n# known from most languages\n#\n# SPDX-License-Identifier: (MIT OR CC0-1.0)\n# Copyright 2020 Jan Tojnar\n# https://github.com/jtojnar/cmake-snips\n#\n# Modelled after Python’s os.path.join\n# https://docs.python.org/3.7/library/os.path.html#os.path.join\n# Windows not supported\nfunction(join_paths joined_path first_path_segment)\n set(temp_path \"${first_path_segment}\")\n foreach(current_segment IN LISTS ARGN)\n if(NOT (\"${current_segment}\" STREQUAL \"\"))\n if(IS_ABSOLUTE \"${current_segment}\")\n set(temp_path \"${current_segment}\")\n else()\n set(temp_path \"${temp_path}/${current_segment}\")\n endif()\n endif()\n endforeach()\n set(${joined_path} \"${temp_path}\" PARENT_SCOPE)\nendfunction()\n" }, { "path": "cmake/mimalloc-config-version.cmake", "content": "set(mi_version_major 2)\nset(mi_version_minor 2)\nset(mi_version_patch 7)\nset(mi_version ${mi_version_major}.${mi_version_minor})\n\nset(PACKAGE_VERSION ${mi_version})\nif(PACKAGE_FIND_VERSION_MAJOR)\n if(\"${PACKAGE_FIND_VERSION_MAJOR}\" EQUAL \"${mi_version_major}\")\n if (\"${PACKAGE_FIND_VERSION_MINOR}\" EQUAL \"${mi_version_minor}\")\n set(PACKAGE_VERSION_EXACT TRUE)\n elseif(\"${PACKAGE_FIND_VERSION_MINOR}\" LESS \"${mi_version_minor}\")\n set(PACKAGE_VERSION_COMPATIBLE TRUE)\n else()\n set(PACKAGE_VERSION_UNSUITABLE TRUE)\n endif()\n else()\n set(PACKAGE_VERSION_UNSUITABLE TRUE)\n endif()\nendif()\n" }, { "path": "cmake/mimalloc-config.cmake", "content": "include(${CMAKE_CURRENT_LIST_DIR}/mimalloc.cmake)\nget_filename_component(MIMALLOC_CMAKE_DIR \"${CMAKE_CURRENT_LIST_DIR}\" PATH) # one up from the cmake dir, e.g. /usr/local/lib/cmake/mimalloc-2.0\nget_filename_component(MIMALLOC_VERSION_DIR \"${CMAKE_CURRENT_LIST_DIR}\" NAME)\nstring(REPLACE \"/lib/cmake\" \"/lib\" MIMALLOC_LIBRARY_DIR \"${MIMALLOC_CMAKE_DIR}\")\nif(\"${MIMALLOC_VERSION_DIR}\" EQUAL \"mimalloc\")\n # top level install\n string(REPLACE \"/lib/cmake\" \"/include\" MIMALLOC_INCLUDE_DIR \"${MIMALLOC_CMAKE_DIR}\")\n set(MIMALLOC_OBJECT_DIR \"${MIMALLOC_LIBRARY_DIR}\")\nelse()\n # versioned\n string(REPLACE \"/lib/cmake/\" \"/include/\" MIMALLOC_INCLUDE_DIR \"${CMAKE_CURRENT_LIST_DIR}\")\n string(REPLACE \"/lib/cmake/\" \"/lib/\" MIMALLOC_OBJECT_DIR \"${CMAKE_CURRENT_LIST_DIR}\")\nendif()\nset(MIMALLOC_TARGET_DIR \"${MIMALLOC_LIBRARY_DIR}\") # legacy\n" }, { "path": "contrib/docker/alpine/Dockerfile", "content": "# alpine image \nFROM alpine\n\n# Install tools\nRUN apk add build-base make cmake\nRUN apk add git\nRUN apk add vim\n\nRUN mkdir -p /home/dev\nWORKDIR /home/dev\n\n# Get mimalloc\nRUN git clone https://github.com/microsoft/mimalloc -b dev2\nRUN mkdir -p mimalloc/out/release\nRUN mkdir -p mimalloc/out/debug\n\n# Build mimalloc debug\nWORKDIR /home/dev/mimalloc/out/debug\nRUN cmake ../.. -DMI_DEBUG_FULL=ON\nRUN make -j\nRUN make test\n\nCMD [\"/bin/sh\"]" }, { "path": "contrib/docker/alpine-arm32v7/Dockerfile", "content": "# install from an image\n# download first an appropriate tar.gz image into the current directory\n# from \nFROM scratch\n\n# Substitute the image name that was downloaded\nADD alpine-minirootfs-20240329-armv7.tar.gz /\n\n# Install tools\nRUN apk add build-base make cmake\nRUN apk add git\nRUN apk add vim\n\nRUN mkdir -p /home/dev\nWORKDIR /home/dev\n\n# Get mimalloc\nRUN git clone https://github.com/microsoft/mimalloc -b dev2\nRUN mkdir -p mimalloc/out/release\nRUN mkdir -p mimalloc/out/debug\n\n# Build mimalloc debug\nWORKDIR /home/dev/mimalloc/out/debug\nRUN cmake ../.. -DMI_DEBUG_FULL=ON\nRUN make -j\nRUN make test\n\nCMD [\"/bin/sh\"]\n" }, { "path": "contrib/docker/alpine-x86/Dockerfile", "content": "# install from an image\n# download first an appropriate tar.gz image into the current directory\n# from \nFROM scratch\n\n# Substitute the image name that was downloaded\nADD alpine-minirootfs-20250108-x86.tar.gz /\n\n# Install tools\nRUN apk add build-base make cmake\nRUN apk add git\nRUN apk add vim\n\nRUN mkdir -p /home/dev\nWORKDIR /home/dev\n\n# Get mimalloc\nRUN git clone https://github.com/microsoft/mimalloc -b dev2\nRUN mkdir -p mimalloc/out/release\nRUN mkdir -p mimalloc/out/debug\n\n# Build mimalloc debug\nWORKDIR /home/dev/mimalloc/out/debug\nRUN cmake ../.. -DMI_DEBUG_FULL=ON\n# RUN make -j\n# RUN make test\n\nCMD [\"/bin/sh\"]\n" }, { "path": "contrib/docker/manylinux-x64/Dockerfile", "content": "FROM quay.io/pypa/manylinux2014_x86_64\n\n# Install tools\nRUN yum install -y openssl-devel\nRUN yum install -y gcc gcc-c++ kernel-devel make\nRUN yum install -y git cmake\nRUN yum install -y vim\n\nRUN mkdir -p /home/dev\nWORKDIR /home/dev\n\n# Get mimalloc\nRUN git clone https://github.com/microsoft/mimalloc -b dev2\nRUN mkdir -p mimalloc/out/release\nRUN mkdir -p mimalloc/out/debug\n\n# Build mimalloc debug\nWORKDIR /home/dev/mimalloc/out/debug\nRUN cmake ../.. -DMI_DEBUG_FULL=ON\nRUN make -j\nRUN make test\n\nCMD [\"/bin/sh\"]" }, { "path": "contrib/docker/readme.md", "content": "Various example docker files used for testing.\n\nUsage:\n\n```\n> cd \n> docker build -t -mimalloc .\n> docker run -it -mimalloc\n>> make test\n```\n" }, { "path": "contrib/nuget/nuget-release-pipeline.yml", "content": "# Microsoft.Mimalloc NuGet Release Pipeline\n# Manually triggered pipeline to build, sign, and publish the mimalloc NuGet package.\n# Builds x64 and ARM64 Windows binaries, signs via ESRP, and packs NuGet.\n\ntrigger: none\npr: none\n\nparameters:\n - name: version\n displayName: 'NuGet package version'\n type: string\n default: '1.0.0'\n\n - name: buildConfig\n displayName: 'Build configuration'\n type: string\n default: 'Release'\n values:\n - Release\n - Debug\n\n - name: signBinaries\n displayName: 'Sign binaries (ESRP)?'\n type: string\n default: 'No'\n values:\n - 'Yes'\n - 'No'\n\n - name: publishToFeed\n displayName: 'Publish NuGet to artifact feed?'\n type: boolean\n default: false\n\nvariables:\n nuspecPath: '$(Build.SourcesDirectory)/contrib/nuget/Microsoft.Mimalloc.nuspec'\n artifactStaging: '$(Build.ArtifactStagingDirectory)'\n" }, { "path": "contrib/vcpkg/portfile.cmake", "content": "vcpkg_from_github(\n OUT_SOURCE_PATH SOURCE_PATH\n REPO microsoft/mimalloc\n HEAD_REF master\n\n # The \"REF\" can be a commit hash, branch name (dev3), or a version (v3.2.7).\n REF \"v${VERSION}\"\n # REF e2db21e9ba9fb9172b7b0aa0fe9b8742525e8774\n\n # The sha512 is the hash of the tar.gz bundle.\n # (To get the sha512, run `vcpkg install \"mimalloc[override]\" --overlay-ports=

` and copy the sha from the error message.)\n SHA512 5830ceb1bf0d02f50fe586caaad87624ba8eba1bb66e68e8201894221cf6f51854f5a9667fc98358c3b430dae6f9bf529bfcb74d42debe6f40a487265053371c\n)\n\nvcpkg_check_features(OUT_FEATURE_OPTIONS FEATURE_OPTIONS\n FEATURES\n c MI_NO_USE_CXX\n guarded MI_GUARDED\n secure MI_SECURE\n override MI_OVERRIDE\n optarch MI_OPT_ARCH\n nooptarch MI_NO_OPT_ARCH\n optsimd MI_OPT_SIMD\n xmalloc MI_XMALLOC\n asm MI_SEE_ASM\n)\nstring(COMPARE EQUAL \"${VCPKG_LIBRARY_LINKAGE}\" \"static\" MI_BUILD_STATIC)\nstring(COMPARE EQUAL \"${VCPKG_LIBRARY_LINKAGE}\" \"dynamic\" MI_BUILD_SHARED)\n\nvcpkg_cmake_configure(\n SOURCE_PATH \"${SOURCE_PATH}\"\n OPTIONS\n -DMI_USE_CXX=ON\n -DMI_BUILD_TESTS=OFF\n -DMI_BUILD_OBJECT=ON\n -DMI_BUILD_STATIC=${MI_BUILD_STATIC}\n -DMI_BUILD_SHARED=${MI_BUILD_SHARED}\n -DMI_INSTALL_TOPLEVEL=ON\n ${FEATURE_OPTIONS}\n)\n\nvcpkg_cmake_install()\nvcpkg_copy_pdbs()\n\nfile(COPY\n \"${CMAKE_CURRENT_LIST_DIR}/vcpkg-cmake-wrapper.cmake\"\n \"${CMAKE_CURRENT_LIST_DIR}/usage\"\n DESTINATION \"${CURRENT_PACKAGES_DIR}/share/${PORT}\"\n)\nvcpkg_cmake_config_fixup(CONFIG_PATH lib/cmake/mimalloc)\n\nif(VCPKG_LIBRARY_LINKAGE STREQUAL \"dynamic\")\n # todo: why is this needed?\n vcpkg_replace_string(\n \"${CURRENT_PACKAGES_DIR}/include/mimalloc.h\"\n \"!defined(MI_SHARED_LIB)\"\n \"0 // !defined(MI_SHARED_LIB)\"\n )\nendif()\nfile(REMOVE_RECURSE \"${CURRENT_PACKAGES_DIR}/debug/include\")\nfile(REMOVE_RECURSE \"${CURRENT_PACKAGES_DIR}/debug/share\")\n\nvcpkg_fixup_pkgconfig()\nvcpkg_install_copyright(FILE_LIST \"${SOURCE_PATH}/LICENSE\")\n" }, { "path": "contrib/vcpkg/readme.md", "content": "# Vcpkg support\n\nThis directory is meant to provide the sources for the official [vcpkg port] \nof mimalloc, but can also be used to override the official port with\nyour own variant.\n\nFor example, you can edit the [`portfile.cmake`](portfile.cmake) \nto check out a specific commit, version, or branch of mimalloc, or set further options. \nYou can install such custom port as:\n\n```sh\n$ vcpkg install \"mimalloc[override]\" --recurse --overlay-ports=./contrib/vcpkg\n```\n\nThis will also show the correct sha512 hash if you use a custom version.\nAnother way is to refer to the overlay from the [vcpkg-configuration.json](https://learn.microsoft.com/en-us/vcpkg/reference/vcpkg-configuration-json) file.\nSee also the vcpkg [documentation](https://learn.microsoft.com/en-us/vcpkg/produce/update-package-version) for more information.\n\n\n# Using mimalloc from vcpkg\n\nWhen using [cmake with vcpkg](https://learn.microsoft.com/en-us/vcpkg/get_started/get-started?pivots=shell-powershell), \nyou can use mimalloc from the `CMakeLists.txt` as:\n\n```cmake\nfind_package(mimalloc CONFIG REQUIRED)\ntarget_link_libraries(main PRIVATE mimalloc)\n```\n\nSee [`test/CMakeLists.txt](../../test/CMakeLists.txt) for more examples.\n\n\n# Acknowledgements\n\nThe original port for vckpg was contributed by many people, including: @vicroms, @myd7349, @PhoubeHui, @LilyWangL,\n@JonLiu1993, @RT2Code, Remy Tassoux, @wangao, @BillyONeal, @jiayuehua, @dg0yt, @gerar-ryan-immersaview, @nickdademo, \nand @jimwang118 -- Thank you so much!\n\n\n[vcpkg port]: https://github.com/microsoft/vcpkg/tree/master/ports/mimalloc\n" }, { "path": "contrib/vcpkg/usage", "content": "Use the following CMake targets to import mimalloc:\n\n find_package(mimalloc CONFIG REQUIRED)\n target_link_libraries(main PRIVATE mimalloc)\n\nAnd use mimalloc in your sources as:\n\n #include \n #include \n int main(int argc, char** argv) {\n int* p = mi_malloc_tp(int);\n *p = mi_version();\n printf(\"mimalloc version: %d\\n\", *p);\n mi_free(p);\n return 0;\n }\n\nWhen dynamically overriding on Windows, ensure `mimalloc.dll` is linked through some call to\nmimalloc (e.g. `mi_version()`), and that the `mimalloc-redirect.dll` is in the same directory.\nSee https://github.com/microsoft/mimalloc/blob/dev/bin/readme.md for detailed information.\n" }, { "path": "contrib/vcpkg/vcpkg-cmake-wrapper.cmake", "content": "_find_package(${ARGS})\n\nif(CMAKE_CURRENT_LIST_DIR STREQUAL \"${MIMALLOC_CMAKE_DIR}/${MIMALLOC_VERSION_DIR}\")\n set(MIMALLOC_INCLUDE_DIR \"${VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/include\")\n # As in vcpkg.cmake\n if(NOT DEFINED CMAKE_BUILD_TYPE OR CMAKE_BUILD_TYPE MATCHES \"^[Dd][Ee][Bb][Uu][Gg]$\")\n set(MIMALLOC_LIBRARY_DIR \"${VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/debug/lib\")\n else()\n set(MIMALLOC_LIBRARY_DIR \"${VCPKG_INSTALLED_DIR}/${VCPKG_TARGET_TRIPLET}/lib\")\n endif()\n set(MIMALLOC_OBJECT_DIR \"${MIMALLOC_LIBRARY_DIR}\")\n set(MIMALLOC_TARGET_DIR \"${MIMALLOC_LIBRARY_DIR}\")\nendif()\n\n# vcpkg always configures either a static or dynamic library.\n# ensure to always expose the mimalloc target as either the static or dynamic build.\nif(TARGET mimalloc-static AND NOT TARGET mimalloc)\n add_library(mimalloc INTERFACE IMPORTED)\n set_target_properties(mimalloc PROPERTIES INTERFACE_LINK_LIBRARIES mimalloc-static)\nendif()\n" }, { "path": "contrib/vcpkg/vcpkg.json", "content": "{\n \"name\": \"mimalloc\",\n \"version\": \"3.2.8\",\n \"port-version\": 0,\n \"description\": \"Compact general purpose allocator with excellent performance\",\n \"homepage\": \"https://github.com/microsoft/mimalloc\",\n \"license\": \"MIT\",\n \"supports\": \"!uwp\",\n \"dependencies\": [\n {\n \"name\": \"vcpkg-cmake\",\n \"host\": true\n },\n {\n \"name\": \"vcpkg-cmake-config\",\n \"host\": true\n }\n ],\n \"features\": {\n \"c\": {\n \"description\": \"Use C11 compilation (this can still override new/delete)\"\n },\n \"override\": {\n \"description\": \"Override the standard malloc/free interface\"\n },\n \"secure\": {\n \"description\": \"Use full security mitigations (like guard pages and randomization)\"\n },\n \"guarded\": {\n \"description\": \"Use build that support guard pages after objects controlled with MIMALLOC_GUARDED_SAMPLE_RATE\"\n },\n \"xmalloc\": {\n \"description\": \"If out-of-memory, call abort() instead of returning NULL\"\n },\n \"optarch\": {\n \"description\": \"Use architecture specific optimizations (on x64: '-march=haswell;-mavx2', on arm64: '-march=armv8.1-a')\"\n },\n \"nooptarch\": {\n \"description\": \"Do _not_ use architecture specific optimizations (on x64: '-march=haswell;-mavx2', on arm64: '-march=armv8.1-a')\"\n },\n \"optsimd\": {\n \"description\": \"Allow use of SIMD instructions (avx2 or neon) (requires 'optarch' to be enabled)\"\n },\n \"asm\": {\n \"description\": \"Generate assembly files\"\n }\n }\n}" }, { "path": "doc/doxyfile", "content": "# Doxyfile 1.11.0\n\n# This file describes the settings to be used by the documentation system\n# doxygen (www.doxygen.org) for a project.\n#\n# All text after a double hash (##) is considered a comment and is placed in\n# front of the TAG it is preceding.\n#\n# All text after a single hash (#) is considered a comment and will be ignored.\n# The format is:\n# TAG = value [value, ...]\n# For lists, items can also be appended using:\n# TAG += value [value, ...]\n# Values that contain spaces should be placed between quotes (\\\" \\\").\n#\n# Note:\n#\n# Use doxygen to compare the used configuration file with the template\n# configuration file:\n# doxygen -x [configFile]\n# Use doxygen to compare the used configuration file with the template\n# configuration file without replacing the environment variables or CMake type\n# replacement variables:\n# doxygen -x_noenv [configFile]\n\n#---------------------------------------------------------------------------\n# Project related configuration options\n#---------------------------------------------------------------------------\n\n# This tag specifies the encoding used for all characters in the configuration\n# file that follow. The default is UTF-8 which is also the encoding used for all\n# text before the first occurrence of this tag. Doxygen uses libiconv (or the\n# iconv built into libc) for the transcoding. See\n# https://www.gnu.org/software/libiconv/ for the list of possible encodings.\n# The default value is: UTF-8.\n\nDOXYFILE_ENCODING = UTF-8\n\n# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by\n# double-quotes, unless you are using Doxywizard) that should identify the\n# project for which the documentation is generated. This name is used in the\n# title of most generated pages and in a few other places.\n# The default value is: My Project.\n\nPROJECT_NAME = mi-malloc\n\n# The PROJECT_NUMBER tag can be used to enter a project or revision number. This\n# could be handy for archiving the generated documentation or if some version\n# control system is used.\n\nPROJECT_NUMBER = 1.8/2.1\n\n# Using the PROJECT_BRIEF tag one can provide an optional one line description\n# for a project that appears at the top of each page and should give viewer a\n# quick idea about the purpose of the project. Keep the description short.\n\nPROJECT_BRIEF =\n\n# With the PROJECT_LOGO tag one can specify a logo or an icon that is included\n# in the documentation. The maximum height of the logo should not exceed 55\n# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy\n# the logo to the output directory.\n\nPROJECT_LOGO = mimalloc-logo.svg\n\n# With the PROJECT_ICON tag one can specify an icon that is included in the tabs\n# when the HTML document is shown. Doxygen will copy the logo to the output\n# directory.\n\nPROJECT_ICON =\n\n# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path\n# into which the generated documentation will be written. If a relative path is\n# entered, it will be relative to the location where doxygen was started. If\n# left blank the current directory will be used.\n\nOUTPUT_DIRECTORY = ..\n\n# If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096\n# sub-directories (in 2 levels) under the output directory of each output format\n# and will distribute the generated files over these directories. Enabling this\n# option can be useful when feeding doxygen a huge amount of source files, where\n# putting all generated files in the same directory would otherwise causes\n# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to\n# control the number of sub-directories.\n# The default value is: NO.\n\nCREATE_SUBDIRS = NO\n\n# Controls the number of sub-directories that will be created when\n# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every\n# level increment doubles the number of directories, resulting in 4096\n# directories at level 8 which is the default and also the maximum value. The\n# sub-directories are organized in 2 levels, the first level always has a fixed\n# number of 16 directories.\n# Minimum value: 0, maximum value: 8, default value: 8.\n# This tag requires that the tag CREATE_SUBDIRS is set to YES.\n\nCREATE_SUBDIRS_LEVEL = 8\n\n# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII\n# characters to appear in the names of generated files. If set to NO, non-ASCII\n# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode\n# U+3044.\n# The default value is: NO.\n\nALLOW_UNICODE_NAMES = NO\n\n# The OUTPUT_LANGUAGE tag is used to specify the language in which all\n# documentation generated by doxygen is written. Doxygen will use this\n# information to generate all constant output in the proper language.\n# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian,\n# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English\n# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek,\n# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with\n# English messages), Korean, Korean-en (Korean with English messages), Latvian,\n# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese,\n# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,\n# Swedish, Turkish, Ukrainian and Vietnamese.\n# The default value is: English.\n\nOUTPUT_LANGUAGE = English\n\n# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member\n# descriptions after the members that are listed in the file and class\n# documentation (similar to Javadoc). Set to NO to disable this.\n# The default value is: YES.\n\nBRIEF_MEMBER_DESC = YES\n\n# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief\n# description of a member or function before the detailed description\n#\n# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the\n# brief descriptions will be completely suppressed.\n# The default value is: YES.\n\nREPEAT_BRIEF = YES\n\n# This tag implements a quasi-intelligent brief description abbreviator that is\n# used to form the text in various listings. Each string in this list, if found\n# as the leading text of the brief description, will be stripped from the text\n# and the result, after processing the whole list, is used as the annotated\n# text. Otherwise, the brief description is used as-is. If left blank, the\n# following values are used ($name is automatically replaced with the name of\n# the entity):The $name class, The $name widget, The $name file, is, provides,\n# specifies, contains, represents, a, an and the.\n\nABBREVIATE_BRIEF = \"The $name class\" \\\n \"The $name widget\" \\\n \"The $name file\" \\\n is \\\n provides \\\n specifies \\\n contains \\\n represents \\\n a \\\n an \\\n the\n\n# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then\n# doxygen will generate a detailed section even if there is only a brief\n# description.\n# The default value is: NO.\n\nALWAYS_DETAILED_SEC = NO\n\n# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all\n# inherited members of a class in the documentation of that class as if those\n# members were ordinary class members. Constructors, destructors and assignment\n# operators of the base classes will not be shown.\n# The default value is: NO.\n\nINLINE_INHERITED_MEMB = NO\n\n# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path\n# before files name in the file list and in the header files. If set to NO the\n# shortest path that makes the file name unique will be used\n# The default value is: YES.\n\nFULL_PATH_NAMES = YES\n\n# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.\n# Stripping is only done if one of the specified strings matches the left-hand\n# part of the path. The tag can be used to show relative paths in the file list.\n# If left blank the directory from which doxygen is run is used as the path to\n# strip.\n#\n# Note that you can specify absolute paths here, but also relative paths, which\n# will be relative from the directory where doxygen is started.\n# This tag requires that the tag FULL_PATH_NAMES is set to YES.\n\nSTRIP_FROM_PATH =\n\n# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the\n# path mentioned in the documentation of a class, which tells the reader which\n# header file to include in order to use a class. If left blank only the name of\n# the header file containing the class definition is used. Otherwise one should\n# specify the list of include paths that are normally passed to the compiler\n# using the -I flag.\n\nSTRIP_FROM_INC_PATH =\n\n# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but\n# less readable) file names. This can be useful is your file systems doesn't\n# support long names like on DOS, Mac, or CD-ROM.\n# The default value is: NO.\n\nSHORT_NAMES = NO\n\n# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the\n# first line (until the first dot) of a Javadoc-style comment as the brief\n# description. If set to NO, the Javadoc-style will behave just like regular Qt-\n# style comments (thus requiring an explicit @brief command for a brief\n# description.)\n# The default value is: NO.\n\nJAVADOC_AUTOBRIEF = YES\n\n# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line\n# such as\n# /***************\n# as being the beginning of a Javadoc-style comment \"banner\". If set to NO, the\n# Javadoc-style will behave just like regular comments and it will not be\n# interpreted by doxygen.\n# The default value is: NO.\n\nJAVADOC_BANNER = NO\n\n# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first\n# line (until the first dot) of a Qt-style comment as the brief description. If\n# set to NO, the Qt-style will behave just like regular Qt-style comments (thus\n# requiring an explicit \\brief command for a brief description.)\n# The default value is: NO.\n\nQT_AUTOBRIEF = NO\n\n# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a\n# multi-line C++ special comment block (i.e. a block of //! or /// comments) as\n# a brief description. This used to be the default behavior. The new default is\n# to treat a multi-line C++ comment block as a detailed description. Set this\n# tag to YES if you prefer the old behavior instead.\n#\n# Note that setting this tag to YES also means that rational rose comments are\n# not recognized any more.\n# The default value is: NO.\n\nMULTILINE_CPP_IS_BRIEF = NO\n\n# By default Python docstrings are displayed as preformatted text and doxygen's\n# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the\n# doxygen's special commands can be used and the contents of the docstring\n# documentation blocks is shown as doxygen documentation.\n# The default value is: YES.\n\nPYTHON_DOCSTRING = YES\n\n# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the\n# documentation from any documented member that it re-implements.\n# The default value is: YES.\n\nINHERIT_DOCS = YES\n\n# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new\n# page for each member. If set to NO, the documentation of a member will be part\n# of the file/class/namespace that contains it.\n# The default value is: NO.\n\nSEPARATE_MEMBER_PAGES = NO\n\n# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen\n# uses this value to replace tabs by spaces in code fragments.\n# Minimum value: 1, maximum value: 16, default value: 4.\n\nTAB_SIZE = 2\n\n# This tag can be used to specify a number of aliases that act as commands in\n# the documentation. An alias has the form:\n# name=value\n# For example adding\n# \"sideeffect=@par Side Effects:^^\"\n# will allow you to put the command \\sideeffect (or @sideeffect) in the\n# documentation, which will result in a user-defined paragraph with heading\n# \"Side Effects:\". Note that you cannot put \\n's in the value part of an alias\n# to insert newlines (in the resulting output). You can put ^^ in the value part\n# of an alias to insert a newline as if a physical newline was in the original\n# file. When you need a literal { or } or , in the value part of an alias you\n# have to escape them by means of a backslash (\\), this can lead to conflicts\n# with the commands \\{ and \\} for these it is advised to use the version @{ and\n# @} or use a double escape (\\\\{ and \\\\})\n\nALIASES =\n\n# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources\n# only. Doxygen will then generate output that is more tailored for C. For\n# instance, some of the names that are used will be different. The list of all\n# members will be omitted, etc.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_FOR_C = YES\n\n# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or\n# Python sources only. Doxygen will then generate output that is more tailored\n# for that language. For instance, namespaces will be presented as packages,\n# qualified scopes will look different, etc.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_JAVA = NO\n\n# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran\n# sources. Doxygen will then generate output that is tailored for Fortran.\n# The default value is: NO.\n\nOPTIMIZE_FOR_FORTRAN = NO\n\n# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL\n# sources. Doxygen will then generate output that is tailored for VHDL.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_VHDL = NO\n\n# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice\n# sources only. Doxygen will then generate output that is more tailored for that\n# language. For instance, namespaces will be presented as modules, types will be\n# separated into more groups, etc.\n# The default value is: NO.\n\nOPTIMIZE_OUTPUT_SLICE = NO\n\n# Doxygen selects the parser to use depending on the extension of the files it\n# parses. With this tag you can assign which parser to use for a given\n# extension. Doxygen has a built-in mapping, but you can override or extend it\n# using this tag. The format is ext=language, where ext is a file extension, and\n# language is one of the parsers supported by doxygen: IDL, Java, JavaScript,\n# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,\n# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:\n# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser\n# tries to guess whether the code is fixed or free formatted code, this is the\n# default for Fortran type files). For instance to make doxygen treat .inc files\n# as Fortran files (default is PHP), and .f files as C (default is Fortran),\n# use: inc=Fortran f=C.\n#\n# Note: For files without extension you can use no_extension as a placeholder.\n#\n# Note that for custom extensions you also need to set FILE_PATTERNS otherwise\n# the files are not read by doxygen. When specifying no_extension you should add\n# * to the FILE_PATTERNS.\n#\n# Note see also the list of default file extension mappings.\n\nEXTENSION_MAPPING =\n\n# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments\n# according to the Markdown format, which allows for more readable\n# documentation. See https://daringfireball.net/projects/markdown/ for details.\n# The output of markdown processing is further processed by doxygen, so you can\n# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in\n# case of backward compatibilities issues.\n# The default value is: YES.\n\nMARKDOWN_SUPPORT = YES\n\n# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up\n# to that level are automatically included in the table of contents, even if\n# they do not have an id attribute.\n# Note: This feature currently applies only to Markdown headings.\n# Minimum value: 0, maximum value: 99, default value: 6.\n# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n\nTOC_INCLUDE_HEADINGS = 0\n\n# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to\n# generate identifiers for the Markdown headings. Note: Every identifier is\n# unique.\n# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a\n# sequence number starting at 0 and GITHUB use the lower case version of title\n# with any whitespace replaced by '-' and punctuation characters removed.\n# The default value is: DOXYGEN.\n# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.\n\nMARKDOWN_ID_STYLE = DOXYGEN\n\n# When enabled doxygen tries to link words that correspond to documented\n# classes, or namespaces to their corresponding documentation. Such a link can\n# be prevented in individual cases by putting a % sign in front of the word or\n# globally by setting AUTOLINK_SUPPORT to NO.\n# The default value is: YES.\n\nAUTOLINK_SUPPORT = YES\n\n# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want\n# to include (a tag file for) the STL sources as input, then you should set this\n# tag to YES in order to let doxygen match functions declarations and\n# definitions whose arguments contain STL classes (e.g. func(std::string);\n# versus func(std::string) {}). This also makes the inheritance and\n# collaboration diagrams that involve STL classes more complete and accurate.\n# The default value is: NO.\n\nBUILTIN_STL_SUPPORT = NO\n\n# If you use Microsoft's C++/CLI language, you should set this option to YES to\n# enable parsing support.\n# The default value is: NO.\n\nCPP_CLI_SUPPORT = NO\n\n# Set the SIP_SUPPORT tag to YES if your project consists of sip (see:\n# https://www.riverbankcomputing.com/software) sources only. Doxygen will parse\n# them like normal C++ but will assume all classes use public instead of private\n# inheritance when no explicit protection keyword is present.\n# The default value is: NO.\n\nSIP_SUPPORT = NO\n\n# For Microsoft's IDL there are propget and propput attributes to indicate\n# getter and setter methods for a property. Setting this option to YES will make\n# doxygen to replace the get and set methods by a property in the documentation.\n# This will only work if the methods are indeed getting or setting a simple\n# type. If this is not the case, or you want to show the methods anyway, you\n# should set this option to NO.\n# The default value is: YES.\n\nIDL_PROPERTY_SUPPORT = YES\n\n# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC\n# tag is set to YES then doxygen will reuse the documentation of the first\n# member in the group (if any) for the other members of the group. By default\n# all members of a group must be documented explicitly.\n# The default value is: NO.\n\nDISTRIBUTE_GROUP_DOC = NO\n\n# If one adds a struct or class to a group and this option is enabled, then also\n# any nested class or struct is added to the same group. By default this option\n# is disabled and one has to add nested compounds explicitly via \\ingroup.\n# The default value is: NO.\n\nGROUP_NESTED_COMPOUNDS = NO\n\n# Set the SUBGROUPING tag to YES to allow class member groups of the same type\n# (for instance a group of public functions) to be put as a subgroup of that\n# type (e.g. under the Public Functions section). Set it to NO to prevent\n# subgrouping. Alternatively, this can be done per class using the\n# \\nosubgrouping command.\n# The default value is: YES.\n\nSUBGROUPING = YES\n\n# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions\n# are shown inside the group in which they are included (e.g. using \\ingroup)\n# instead of on a separate page (for HTML and Man pages) or section (for LaTeX\n# and RTF).\n#\n# Note that this feature does not work in combination with\n# SEPARATE_MEMBER_PAGES.\n# The default value is: NO.\n\nINLINE_GROUPED_CLASSES = NO\n\n# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions\n# with only public data fields or simple typedef fields will be shown inline in\n# the documentation of the scope in which they are defined (i.e. file,\n# namespace, or group documentation), provided this scope is documented. If set\n# to NO, structs, classes, and unions are shown on a separate page (for HTML and\n# Man pages) or section (for LaTeX and RTF).\n# The default value is: NO.\n\nINLINE_SIMPLE_STRUCTS = YES\n\n# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or\n# enum is documented as struct, union, or enum with the name of the typedef. So\n# typedef struct TypeS {} TypeT, will appear in the documentation as a struct\n# with name TypeT. When disabled the typedef will appear as a member of a file,\n# namespace, or class. And the struct will be named TypeS. This can typically be\n# useful for C code in case the coding convention dictates that all compound\n# types are typedef'ed and only the typedef is referenced, never the tag name.\n# The default value is: NO.\n\nTYPEDEF_HIDES_STRUCT = YES\n\n# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This\n# cache is used to resolve symbols given their name and scope. Since this can be\n# an expensive process and often the same symbol appears multiple times in the\n# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small\n# doxygen will become slower. If the cache is too large, memory is wasted. The\n# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range\n# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536\n# symbols. At the end of a run doxygen will report the cache usage and suggest\n# the optimal cache size from a speed point of view.\n# Minimum value: 0, maximum value: 9, default value: 0.\n\nLOOKUP_CACHE_SIZE = 0\n\n# The NUM_PROC_THREADS specifies the number of threads doxygen is allowed to use\n# during processing. When set to 0 doxygen will based this on the number of\n# cores available in the system. You can set it explicitly to a value larger\n# than 0 to get more control over the balance between CPU load and processing\n# speed. At this moment only the input processing can be done using multiple\n# threads. Since this is still an experimental feature the default is set to 1,\n# which effectively disables parallel processing. Please report any issues you\n# encounter. Generating dot graphs in parallel is controlled by the\n# DOT_NUM_THREADS setting.\n# Minimum value: 0, maximum value: 32, default value: 1.\n\nNUM_PROC_THREADS = 1\n\n# If the TIMESTAMP tag is set different from NO then each generated page will\n# contain the date or date and time when the page was generated. Setting this to\n# NO can help when comparing the output of multiple runs.\n# Possible values are: YES, NO, DATETIME and DATE.\n# The default value is: NO.\n\nTIMESTAMP = NO\n\n#---------------------------------------------------------------------------\n# Build related configuration options\n#---------------------------------------------------------------------------\n\n# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in\n# documentation are documented, even if no documentation was available. Private\n# class members and static file members will be hidden unless the\n# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.\n# Note: This will also disable the warnings about undocumented members that are\n# normally produced when WARNINGS is set to YES.\n# The default value is: NO.\n\nEXTRACT_ALL = YES\n\n# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will\n# be included in the documentation.\n# The default value is: NO.\n\nEXTRACT_PRIVATE = NO\n\n# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual\n# methods of a class will be included in the documentation.\n# The default value is: NO.\n\nEXTRACT_PRIV_VIRTUAL = NO\n\n# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal\n# scope will be included in the documentation.\n# The default value is: NO.\n\nEXTRACT_PACKAGE = NO\n\n# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be\n# included in the documentation.\n# The default value is: NO.\n\nEXTRACT_STATIC = NO\n\n# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined\n# locally in source files will be included in the documentation. If set to NO,\n# only classes defined in header files are included. Does not have any effect\n# for Java sources.\n# The default value is: YES.\n\nEXTRACT_LOCAL_CLASSES = YES\n\n# This flag is only useful for Objective-C code. If set to YES, local methods,\n# which are defined in the implementation section but not in the interface are\n# included in the documentation. If set to NO, only methods in the interface are\n# included.\n# The default value is: NO.\n\nEXTRACT_LOCAL_METHODS = NO\n\n# If this flag is set to YES, the members of anonymous namespaces will be\n# extracted and appear in the documentation as a namespace called\n# 'anonymous_namespace{file}', where file will be replaced with the base name of\n# the file that contains the anonymous namespace. By default anonymous namespace\n# are hidden.\n# The default value is: NO.\n\nEXTRACT_ANON_NSPACES = NO\n\n# If this flag is set to YES, the name of an unnamed parameter in a declaration\n# will be determined by the corresponding definition. By default unnamed\n# parameters remain unnamed in the output.\n# The default value is: YES.\n\nRESOLVE_UNNAMED_PARAMS = YES\n\n# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all\n# undocumented members inside documented classes or files. If set to NO these\n# members will be included in the various overviews, but no documentation\n# section is generated. This option has no effect if EXTRACT_ALL is enabled.\n# The default value is: NO.\n\nHIDE_UNDOC_MEMBERS = NO\n\n# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all\n# undocumented classes that are normally visible in the class hierarchy. If set\n# to NO, these classes will be included in the various overviews. This option\n# will also hide undocumented C++ concepts if enabled. This option has no effect\n# if EXTRACT_ALL is enabled.\n# The default value is: NO.\n\nHIDE_UNDOC_CLASSES = NO\n\n# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend\n# declarations. If set to NO, these declarations will be included in the\n# documentation.\n# The default value is: NO.\n\nHIDE_FRIEND_COMPOUNDS = NO\n\n# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any\n# documentation blocks found inside the body of a function. If set to NO, these\n# blocks will be appended to the function's detailed documentation block.\n# The default value is: NO.\n\nHIDE_IN_BODY_DOCS = NO\n\n# The INTERNAL_DOCS tag determines if documentation that is typed after a\n# \\internal command is included. If the tag is set to NO then the documentation\n# will be excluded. Set it to YES to include the internal documentation.\n# The default value is: NO.\n\nINTERNAL_DOCS = NO\n\n# With the correct setting of option CASE_SENSE_NAMES doxygen will better be\n# able to match the capabilities of the underlying filesystem. In case the\n# filesystem is case sensitive (i.e. it supports files in the same directory\n# whose names only differ in casing), the option must be set to YES to properly\n# deal with such files in case they appear in the input. For filesystems that\n# are not case sensitive the option should be set to NO to properly deal with\n# output files written for symbols that only differ in casing, such as for two\n# classes, one named CLASS and the other named Class, and to also support\n# references to files without having to specify the exact matching casing. On\n# Windows (including Cygwin) and MacOS, users should typically set this option\n# to NO, whereas on Linux or other Unix flavors it should typically be set to\n# YES.\n# Possible values are: SYSTEM, NO and YES.\n# The default value is: SYSTEM.\n\nCASE_SENSE_NAMES = NO\n\n# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with\n# their full class and namespace scopes in the documentation. If set to YES, the\n# scope will be hidden.\n# The default value is: NO.\n\nHIDE_SCOPE_NAMES = NO\n\n# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will\n# append additional text to a page's title, such as Class Reference. If set to\n# YES the compound reference will be hidden.\n# The default value is: NO.\n\nHIDE_COMPOUND_REFERENCE= NO\n\n# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class\n# will show which file needs to be included to use the class.\n# The default value is: YES.\n\nSHOW_HEADERFILE = YES\n\n# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of\n# the files that are included by a file in the documentation of that file.\n# The default value is: YES.\n\nSHOW_INCLUDE_FILES = YES\n\n# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each\n# grouped member an include statement to the documentation, telling the reader\n# which file to include in order to use the member.\n# The default value is: NO.\n\nSHOW_GROUPED_MEMB_INC = NO\n\n# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include\n# files with double quotes in the documentation rather than with sharp brackets.\n# The default value is: NO.\n\nFORCE_LOCAL_INCLUDES = NO\n\n# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the\n# documentation for inline members.\n# The default value is: YES.\n\nINLINE_INFO = YES\n\n# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the\n# (detailed) documentation of file and class members alphabetically by member\n# name. If set to NO, the members will appear in declaration order.\n# The default value is: YES.\n\nSORT_MEMBER_DOCS = YES\n\n# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief\n# descriptions of file, namespace and class members alphabetically by member\n# name. If set to NO, the members will appear in declaration order. Note that\n# this will also influence the order of the classes in the class list.\n# The default value is: NO.\n\nSORT_BRIEF_DOCS = NO\n\n# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the\n# (brief and detailed) documentation of class members so that constructors and\n# destructors are listed first. If set to NO the constructors will appear in the\n# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.\n# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief\n# member documentation.\n# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting\n# detailed member documentation.\n# The default value is: NO.\n\nSORT_MEMBERS_CTORS_1ST = NO\n\n# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy\n# of group names into alphabetical order. If set to NO the group names will\n# appear in their defined order.\n# The default value is: NO.\n\nSORT_GROUP_NAMES = NO\n\n# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by\n# fully-qualified names, including namespaces. If set to NO, the class list will\n# be sorted only by class name, not including the namespace part.\n# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.\n# Note: This option applies only to the class list, not to the alphabetical\n# list.\n# The default value is: NO.\n\nSORT_BY_SCOPE_NAME = NO\n\n# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper\n# type resolution of all parameters of a function it will reject a match between\n# the prototype and the implementation of a member function even if there is\n# only one candidate or it is obvious which candidate to choose by doing a\n# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still\n# accept a match between prototype and implementation in such cases.\n# The default value is: NO.\n\nSTRICT_PROTO_MATCHING = NO\n\n# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo\n# list. This list is created by putting \\todo commands in the documentation.\n# The default value is: YES.\n\nGENERATE_TODOLIST = YES\n\n# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test\n# list. This list is created by putting \\test commands in the documentation.\n# The default value is: YES.\n\nGENERATE_TESTLIST = YES\n\n# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug\n# list. This list is created by putting \\bug commands in the documentation.\n# The default value is: YES.\n\nGENERATE_BUGLIST = YES\n\n# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)\n# the deprecated list. This list is created by putting \\deprecated commands in\n# the documentation.\n# The default value is: YES.\n\nGENERATE_DEPRECATEDLIST= YES\n\n# The ENABLED_SECTIONS tag can be used to enable conditional documentation\n# sections, marked by \\if ... \\endif and \\cond \n# ... \\endcond blocks.\n\nENABLED_SECTIONS =\n\n# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the\n# initial value of a variable or macro / define can have for it to appear in the\n# documentation. If the initializer consists of more lines than specified here\n# it will be hidden. Use a value of 0 to hide initializers completely. The\n# appearance of the value of individual variables and macros / defines can be\n# controlled using \\showinitializer or \\hideinitializer command in the\n# documentation regardless of this setting.\n# Minimum value: 0, maximum value: 10000, default value: 30.\n\nMAX_INITIALIZER_LINES = 0\n\n# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at\n# the bottom of the documentation of classes and structs. If set to YES, the\n# list will mention the files that were used to generate the documentation.\n# The default value is: YES.\n\nSHOW_USED_FILES = NO\n\n# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This\n# will remove the Files entry from the Quick Index and from the Folder Tree View\n# (if specified).\n# The default value is: YES.\n\nSHOW_FILES = NO\n\n# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces\n# page. This will remove the Namespaces entry from the Quick Index and from the\n# Folder Tree View (if specified).\n# The default value is: YES.\n\nSHOW_NAMESPACES = YES\n\n# The FILE_VERSION_FILTER tag can be used to specify a program or script that\n# doxygen should invoke to get the current version for each file (typically from\n# the version control system). Doxygen will invoke the program by executing (via\n# popen()) the command command input-file, where command is the value of the\n# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided\n# by doxygen. Whatever the program writes to standard output is used as the file\n# version. For an example see the documentation.\n\nFILE_VERSION_FILTER =\n\n# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed\n# by doxygen. The layout file controls the global structure of the generated\n# output files in an output format independent way. To create the layout file\n# that represents doxygen's defaults, run doxygen with the -l option. You can\n# optionally specify a file name after the option, if omitted DoxygenLayout.xml\n# will be used as the name of the layout file. See also section \"Changing the\n# layout of pages\" for information.\n#\n# Note that if you run doxygen from a directory containing a file called\n# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE\n# tag is left empty.\n\nLAYOUT_FILE =\n\n# The CITE_BIB_FILES tag can be used to specify one or more bib files containing\n# the reference definitions. This must be a list of .bib files. The .bib\n# extension is automatically appended if omitted. This requires the bibtex tool\n# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.\n# For LaTeX the style of the bibliography can be controlled using\n# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the\n# search path. See also \\cite for info how to create references.\n\nCITE_BIB_FILES =\n\n#---------------------------------------------------------------------------\n# Configuration options related to warning and progress messages\n#---------------------------------------------------------------------------\n\n# The QUIET tag can be used to turn on/off the messages that are generated to\n# standard output by doxygen. If QUIET is set to YES this implies that the\n# messages are off.\n# The default value is: NO.\n\nQUIET = NO\n\n# The WARNINGS tag can be used to turn on/off the warning messages that are\n# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES\n# this implies that the warnings are on.\n#\n# Tip: Turn warnings on while writing the documentation.\n# The default value is: YES.\n\nWARNINGS = YES\n\n# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate\n# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag\n# will automatically be disabled.\n# The default value is: YES.\n\nWARN_IF_UNDOCUMENTED = YES\n\n# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for\n# potential errors in the documentation, such as documenting some parameters in\n# a documented function twice, or documenting parameters that don't exist or\n# using markup commands wrongly.\n# The default value is: YES.\n\nWARN_IF_DOC_ERROR = YES\n\n# If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete\n# function parameter documentation. If set to NO, doxygen will accept that some\n# parameters have no documentation without warning.\n# The default value is: YES.\n\nWARN_IF_INCOMPLETE_DOC = YES\n\n# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that\n# are documented, but have no documentation for their parameters or return\n# value. If set to NO, doxygen will only warn about wrong parameter\n# documentation, but not about the absence of documentation. If EXTRACT_ALL is\n# set to YES then this flag will automatically be disabled. See also\n# WARN_IF_INCOMPLETE_DOC\n# The default value is: NO.\n\nWARN_NO_PARAMDOC = NO\n\n# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, doxygen will warn about\n# undocumented enumeration values. If set to NO, doxygen will accept\n# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag\n# will automatically be disabled.\n# The default value is: NO.\n\nWARN_IF_UNDOC_ENUM_VAL = NO\n\n# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when\n# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS\n# then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but\n# at the end of the doxygen process doxygen will return with a non-zero status.\n# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then doxygen behaves\n# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined doxygen will not\n# write the warning messages in between other messages but write them at the end\n# of a run, in case a WARN_LOGFILE is defined the warning messages will be\n# besides being in the defined file also be shown at the end of a run, unless\n# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case\n# the behavior will remain as with the setting FAIL_ON_WARNINGS.\n# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT.\n# The default value is: NO.\n\nWARN_AS_ERROR = NO\n\n# The WARN_FORMAT tag determines the format of the warning messages that doxygen\n# can produce. The string should contain the $file, $line, and $text tags, which\n# will be replaced by the file and line number from which the warning originated\n# and the warning text. Optionally the format may contain $version, which will\n# be replaced by the version of the file (if it could be obtained via\n# FILE_VERSION_FILTER)\n# See also: WARN_LINE_FORMAT\n# The default value is: $file:$line: $text.\n\nWARN_FORMAT = \"$file:$line: $text\"\n\n# In the $text part of the WARN_FORMAT command it is possible that a reference\n# to a more specific place is given. To make it easier to jump to this place\n# (outside of doxygen) the user can define a custom \"cut\" / \"paste\" string.\n# Example:\n# WARN_LINE_FORMAT = \"'vi $file +$line'\"\n# See also: WARN_FORMAT\n# The default value is: at line $line of file $file.\n\nWARN_LINE_FORMAT = \"at line $line of file $file\"\n\n# The WARN_LOGFILE tag can be used to specify a file to which warning and error\n# messages should be written. If left blank the output is written to standard\n# error (stderr). In case the file specified cannot be opened for writing the\n# warning and error messages are written to standard error. When as file - is\n# specified the warning and error messages are written to standard output\n# (stdout).\n\nWARN_LOGFILE =\n\n#---------------------------------------------------------------------------\n# Configuration options related to the input files\n#---------------------------------------------------------------------------\n\n# The INPUT tag is used to specify the files and/or directories that contain\n# documented source files. You may enter file names like myfile.cpp or\n# directories like /usr/src/myproject. Separate the files or directories with\n# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING\n# Note: If this tag is empty the current directory is searched.\n\nINPUT = mimalloc-doc.h\n\n# This tag can be used to specify the character encoding of the source files\n# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses\n# libiconv (or the iconv built into libc) for the transcoding. See the libiconv\n# documentation (see:\n# https://www.gnu.org/software/libiconv/) for the list of possible encodings.\n# See also: INPUT_FILE_ENCODING\n# The default value is: UTF-8.\n\nINPUT_ENCODING = UTF-8\n\n# This tag can be used to specify the character encoding of the source files\n# that doxygen parses The INPUT_FILE_ENCODING tag can be used to specify\n# character encoding on a per file pattern basis. Doxygen will compare the file\n# name with each pattern and apply the encoding instead of the default\n# INPUT_ENCODING) if there is a match. The character encodings are a list of the\n# form: pattern=encoding (like *.php=ISO-8859-1).\n# See also: INPUT_ENCODING for further information on supported encodings.\n\nINPUT_FILE_ENCODING =\n\n# If the value of the INPUT tag contains directories, you can use the\n# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and\n# *.h) to filter out the source-files in the directories.\n#\n# Note that for custom extensions or not directly supported extensions you also\n# need to set EXTENSION_MAPPING for the extension otherwise the files are not\n# read by doxygen.\n#\n# Note the list of default checked file patterns might differ from the list of\n# default file extension mappings.\n#\n# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,\n# *.cpp, *.cppm, *.ccm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl,\n# *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.ixx, *.l, *.cs, *.d,\n# *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to\n# be provided as doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,\n# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.\n\nFILE_PATTERNS = *.c \\\n *.cc \\\n *.cxx \\\n *.cpp \\\n *.c++ \\\n *.java \\\n *.ii \\\n *.ixx \\\n *.ipp \\\n *.i++ \\\n *.inl \\\n *.idl \\\n *.ddl \\\n *.odl \\\n *.h \\\n *.hh \\\n *.hxx \\\n *.hpp \\\n *.h++ \\\n *.cs \\\n *.d \\\n *.php \\\n *.php4 \\\n *.php5 \\\n *.phtml \\\n *.inc \\\n *.m \\\n *.markdown \\\n *.md \\\n *.mm \\\n *.dox \\\n *.py \\\n *.pyw \\\n *.f90 \\\n *.f95 \\\n *.f03 \\\n *.f08 \\\n *.f \\\n *.for \\\n *.tcl \\\n *.vhd \\\n *.vhdl \\\n *.ucf \\\n *.qsf\n\n# The RECURSIVE tag can be used to specify whether or not subdirectories should\n# be searched for input files as well.\n# The default value is: NO.\n\nRECURSIVE = NO\n\n# The EXCLUDE tag can be used to specify files and/or directories that should be\n# excluded from the INPUT source files. This way you can easily exclude a\n# subdirectory from a directory tree whose root is specified with the INPUT tag.\n#\n# Note that relative paths are relative to the directory from which doxygen is\n# run.\n\nEXCLUDE =\n\n# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or\n# directories that are symbolic links (a Unix file system feature) are excluded\n# from the input.\n# The default value is: NO.\n\nEXCLUDE_SYMLINKS = NO\n\n# If the value of the INPUT tag contains directories, you can use the\n# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude\n# certain files from those directories.\n#\n# Note that the wildcards are matched against the file with absolute path, so to\n# exclude all test directories for example use the pattern */test/*\n\nEXCLUDE_PATTERNS =\n\n# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names\n# (namespaces, classes, functions, etc.) that should be excluded from the\n# output. The symbol name can be a fully qualified name, a word, or if the\n# wildcard * is used, a substring. Examples: ANamespace, AClass,\n# ANamespace::AClass, ANamespace::*Test\n\nEXCLUDE_SYMBOLS =\n\n# The EXAMPLE_PATH tag can be used to specify one or more files or directories\n# that contain example code fragments that are included (see the \\include\n# command).\n\nEXAMPLE_PATH =\n\n# If the value of the EXAMPLE_PATH tag contains directories, you can use the\n# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and\n# *.h) to filter out the source-files in the directories. If left blank all\n# files are included.\n\nEXAMPLE_PATTERNS = *\n\n# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be\n# searched for input files to be used with the \\include or \\dontinclude commands\n# irrespective of the value of the RECURSIVE tag.\n# The default value is: NO.\n\nEXAMPLE_RECURSIVE = NO\n\n# The IMAGE_PATH tag can be used to specify one or more files or directories\n# that contain images that are to be included in the documentation (see the\n# \\image command).\n\nIMAGE_PATH =\n\n# The INPUT_FILTER tag can be used to specify a program that doxygen should\n# invoke to filter for each input file. Doxygen will invoke the filter program\n# by executing (via popen()) the command:\n#\n# \n#\n# where is the value of the INPUT_FILTER tag, and is the\n# name of an input file. Doxygen will then use the output that the filter\n# program writes to standard output. If FILTER_PATTERNS is specified, this tag\n# will be ignored.\n#\n# Note that the filter must not add or remove lines; it is applied before the\n# code is scanned, but not when the output code is generated. If lines are added\n# or removed, the anchors will not be placed correctly.\n#\n# Note that doxygen will use the data processed and written to standard output\n# for further processing, therefore nothing else, like debug statements or used\n# commands (so in case of a Windows batch file always use @echo OFF), should be\n# written to standard output.\n#\n# Note that for custom extensions or not directly supported extensions you also\n# need to set EXTENSION_MAPPING for the extension otherwise the files are not\n# properly processed by doxygen.\n\nINPUT_FILTER =\n\n# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern\n# basis. Doxygen will compare the file name with each pattern and apply the\n# filter if there is a match. The filters are a list of the form: pattern=filter\n# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how\n# filters are used. If the FILTER_PATTERNS tag is empty or if none of the\n# patterns match the file name, INPUT_FILTER is applied.\n#\n# Note that for custom extensions or not directly supported extensions you also\n# need to set EXTENSION_MAPPING for the extension otherwise the files are not\n# properly processed by doxygen.\n\nFILTER_PATTERNS =\n\n# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using\n# INPUT_FILTER) will also be used to filter the input files that are used for\n# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).\n# The default value is: NO.\n\nFILTER_SOURCE_FILES = NO\n\n# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file\n# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and\n# it is also possible to disable source filtering for a specific pattern using\n# *.ext= (so without naming a filter).\n# This tag requires that the tag FILTER_SOURCE_FILES is set to YES.\n\nFILTER_SOURCE_PATTERNS =\n\n# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that\n# is part of the input, its contents will be placed on the main page\n# (index.html). This can be useful if you have a project on for instance GitHub\n# and want to reuse the introduction page also for the doxygen output.\n\nUSE_MDFILE_AS_MAINPAGE =\n\n# The Fortran standard specifies that for fixed formatted Fortran code all\n# characters from position 72 are to be considered as comment. A common\n# extension is to allow longer lines before the automatic comment starts. The\n# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can\n# be processed before the automatic comment starts.\n# Minimum value: 7, maximum value: 10000, default value: 72.\n\nFORTRAN_COMMENT_AFTER = 72\n\n#---------------------------------------------------------------------------\n# Configuration options related to source browsing\n#---------------------------------------------------------------------------\n\n# If the SOURCE_BROWSER tag is set to YES then a list of source files will be\n# generated. Documented entities will be cross-referenced with these sources.\n#\n# Note: To get rid of all source code in the generated output, make sure that\n# also VERBATIM_HEADERS is set to NO.\n# The default value is: NO.\n\nSOURCE_BROWSER = NO\n\n# Setting the INLINE_SOURCES tag to YES will include the body of functions,\n# multi-line macros, enums or list initialized variables directly into the\n# documentation.\n# The default value is: NO.\n\nINLINE_SOURCES = NO\n\n# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any\n# special comment blocks from generated source code fragments. Normal C, C++ and\n# Fortran comments will always remain visible.\n# The default value is: YES.\n\nSTRIP_CODE_COMMENTS = YES\n\n# If the REFERENCED_BY_RELATION tag is set to YES then for each documented\n# entity all documented functions referencing it will be listed.\n# The default value is: NO.\n\nREFERENCED_BY_RELATION = NO\n\n# If the REFERENCES_RELATION tag is set to YES then for each documented function\n# all documented entities called/used by that function will be listed.\n# The default value is: NO.\n\nREFERENCES_RELATION = NO\n\n# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set\n# to YES then the hyperlinks from functions in REFERENCES_RELATION and\n# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will\n# link to the documentation.\n# The default value is: YES.\n\nREFERENCES_LINK_SOURCE = YES\n\n# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the\n# source code will show a tooltip with additional information such as prototype,\n# brief description and links to the definition and documentation. Since this\n# will make the HTML file larger and loading of large files a bit slower, you\n# can opt to disable this feature.\n# The default value is: YES.\n# This tag requires that the tag SOURCE_BROWSER is set to YES.\n\nSOURCE_TOOLTIPS = YES\n\n# If the USE_HTAGS tag is set to YES then the references to source code will\n# point to the HTML generated by the htags(1) tool instead of doxygen built-in\n# source browser. The htags tool is part of GNU's global source tagging system\n# (see https://www.gnu.org/software/global/global.html). You will need version\n# 4.8.6 or higher.\n#\n# To use it do the following:\n# - Install the latest version of global\n# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file\n# - Make sure the INPUT points to the root of the source tree\n# - Run doxygen as normal\n#\n# Doxygen will invoke htags (and that will in turn invoke gtags), so these\n# tools must be available from the command line (i.e. in the search path).\n#\n# The result: instead of the source browser generated by doxygen, the links to\n# source code will now point to the output of htags.\n# The default value is: NO.\n# This tag requires that the tag SOURCE_BROWSER is set to YES.\n\nUSE_HTAGS = NO\n\n# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a\n# verbatim copy of the header file for each class for which an include is\n# specified. Set to NO to disable this.\n# See also: Section \\class.\n# The default value is: YES.\n\nVERBATIM_HEADERS = YES\n\n# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the\n# clang parser (see:\n# http://clang.llvm.org/) for more accurate parsing at the cost of reduced\n# performance. This can be particularly helpful with template rich C++ code for\n# which doxygen's built-in parser lacks the necessary type information.\n# Note: The availability of this option depends on whether or not doxygen was\n# generated with the -Duse_libclang=ON option for CMake.\n# The default value is: NO.\n\nCLANG_ASSISTED_PARSING = NO\n\n# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS\n# tag is set to YES then doxygen will add the directory of each input to the\n# include path.\n# The default value is: YES.\n# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.\n\nCLANG_ADD_INC_PATHS = YES\n\n# If clang assisted parsing is enabled you can provide the compiler with command\n# line options that you would normally use when invoking the compiler. Note that\n# the include paths will already be set by doxygen for the files and directories\n# specified with INPUT and INCLUDE_PATH.\n# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.\n\nCLANG_OPTIONS =\n\n# If clang assisted parsing is enabled you can provide the clang parser with the\n# path to the directory containing a file called compile_commands.json. This\n# file is the compilation database (see:\n# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the\n# options used when the source files were built. This is equivalent to\n# specifying the -p option to a clang tool, such as clang-check. These options\n# will then be passed to the parser. Any options specified with CLANG_OPTIONS\n# will be added as well.\n# Note: The availability of this option depends on whether or not doxygen was\n# generated with the -Duse_libclang=ON option for CMake.\n\nCLANG_DATABASE_PATH =\n\n#---------------------------------------------------------------------------\n# Configuration options related to the alphabetical class index\n#---------------------------------------------------------------------------\n\n# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all\n# compounds will be generated. Enable this if the project contains a lot of\n# classes, structs, unions or interfaces.\n# The default value is: YES.\n\nALPHABETICAL_INDEX = YES\n\n# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)\n# that should be ignored while generating the index headers. The IGNORE_PREFIX\n# tag works for classes, function and member names. The entity will be placed in\n# the alphabetical list under the first letter of the entity name that remains\n# after removing the prefix.\n# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.\n\nIGNORE_PREFIX =\n\n#---------------------------------------------------------------------------\n# Configuration options related to the HTML output\n#---------------------------------------------------------------------------\n\n# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output\n# The default value is: YES.\n\nGENERATE_HTML = YES\n\n# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a\n# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of\n# it.\n# The default directory is: html.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_OUTPUT = docs\n\n# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each\n# generated HTML page (for example: .htm, .php, .asp).\n# The default value is: .html.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_FILE_EXTENSION = .html\n\n# The HTML_HEADER tag can be used to specify a user-defined HTML header file for\n# each generated HTML page. If the tag is left blank doxygen will generate a\n# standard header.\n#\n# To get valid HTML the header file that includes any scripts and style sheets\n# that doxygen needs, which is dependent on the configuration options used (e.g.\n# the setting GENERATE_TREEVIEW). It is highly recommended to start with a\n# default header using\n# doxygen -w html new_header.html new_footer.html new_stylesheet.css\n# YourConfigFile\n# and then modify the file new_header.html. See also section \"Doxygen usage\"\n# for information on how to generate the default header that doxygen normally\n# uses.\n# Note: The header is subject to change so you typically have to regenerate the\n# default header when upgrading to a newer version of doxygen. For a description\n# of the possible markers and block names see the documentation.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_HEADER =\n\n# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each\n# generated HTML page. If the tag is left blank doxygen will generate a standard\n# footer. See HTML_HEADER for more information on how to generate a default\n# footer and what special commands can be used inside the footer. See also\n# section \"Doxygen usage\" for information on how to generate the default footer\n# that doxygen normally uses.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_FOOTER =\n\n# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style\n# sheet that is used by each HTML page. It can be used to fine-tune the look of\n# the HTML output. If left blank doxygen will generate a default style sheet.\n# See also section \"Doxygen usage\" for information on how to generate the style\n# sheet that doxygen normally uses.\n# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as\n# it is more robust and this tag (HTML_STYLESHEET) will in the future become\n# obsolete.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_STYLESHEET =\n\n# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined\n# cascading style sheets that are included after the standard style sheets\n# created by doxygen. Using this option one can overrule certain style aspects.\n# This is preferred over using HTML_STYLESHEET since it does not replace the\n# standard style sheet and is therefore more robust against future updates.\n# Doxygen will copy the style sheet files to the output directory.\n# Note: The order of the extra style sheet files is of importance (e.g. the last\n# style sheet in the list overrules the setting of the previous ones in the\n# list).\n# Note: Since the styling of scrollbars can currently not be overruled in\n# Webkit/Chromium, the styling will be left out of the default doxygen.css if\n# one or more extra stylesheets have been specified. So if scrollbar\n# customization is desired it has to be added explicitly. For an example see the\n# documentation.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_EXTRA_STYLESHEET = mimalloc-doxygen.css\n\n# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or\n# other source files which should be copied to the HTML output directory. Note\n# that these files will be copied to the base HTML output directory. Use the\n# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these\n# files. In the HTML_STYLESHEET file, use the file name only. Also note that the\n# files will be copied as-is; there are no commands or markers available.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_EXTRA_FILES =\n\n# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output\n# should be rendered with a dark or light theme.\n# Possible values are: LIGHT always generates light mode output, DARK always\n# generates dark mode output, AUTO_LIGHT automatically sets the mode according\n# to the user preference, uses light mode if no preference is set (the default),\n# AUTO_DARK automatically sets the mode according to the user preference, uses\n# dark mode if no preference is set and TOGGLE allows a user to switch between\n# light and dark mode via a button.\n# The default value is: AUTO_LIGHT.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE = LIGHT\n\n# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen\n# will adjust the colors in the style sheet and background images according to\n# this color. Hue is specified as an angle on a color-wheel, see\n# https://en.wikipedia.org/wiki/Hue for more information. For instance the value\n# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300\n# purple, and 360 is red again.\n# Minimum value: 0, maximum value: 359, default value: 220.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE_HUE = 189\n\n# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors\n# in the HTML output. For a value of 0 the output will use gray-scales only. A\n# value of 255 will produce the most vivid colors.\n# Minimum value: 0, maximum value: 255, default value: 100.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE_SAT = 12\n\n# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the\n# luminance component of the colors in the HTML output. Values below 100\n# gradually make the output lighter, whereas values above 100 make the output\n# darker. The value divided by 100 is the actual gamma applied, so 80 represents\n# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not\n# change the gamma.\n# Minimum value: 40, maximum value: 240, default value: 80.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COLORSTYLE_GAMMA = 240\n\n# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML\n# documentation will contain a main index with vertical navigation menus that\n# are dynamically created via JavaScript. If disabled, the navigation index will\n# consists of multiple levels of tabs that are statically embedded in every HTML\n# page. Disable this option to support browsers that do not have JavaScript,\n# like the Qt help browser.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_DYNAMIC_MENUS = NO\n\n# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML\n# documentation will contain sections that can be hidden and shown after the\n# page has loaded.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_DYNAMIC_SECTIONS = NO\n\n# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be\n# dynamically folded and expanded in the generated HTML source code.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_CODE_FOLDING = YES\n\n# If the HTML_COPY_CLIPBOARD tag is set to YES then doxygen will show an icon in\n# the top right corner of code and text fragments that allows the user to copy\n# its content to the clipboard. Note this only works if supported by the browser\n# and the web page is served via a secure context (see:\n# https://www.w3.org/TR/secure-contexts/), i.e. using the https: or file:\n# protocol.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_COPY_CLIPBOARD = YES\n\n# Doxygen stores a couple of settings persistently in the browser (via e.g.\n# cookies). By default these settings apply to all HTML pages generated by\n# doxygen across all projects. The HTML_PROJECT_COOKIE tag can be used to store\n# the settings under a project specific key, such that the user preferences will\n# be stored separately.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_PROJECT_COOKIE =\n\n# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries\n# shown in the various tree structured indices initially; the user can expand\n# and collapse entries dynamically later on. Doxygen will expand the tree to\n# such a level that at most the specified number of entries are visible (unless\n# a fully collapsed tree already exceeds this amount). So setting the number of\n# entries 1 will produce a full collapsed tree by default. 0 is a special value\n# representing an infinite number of entries and will result in a full expanded\n# tree by default.\n# Minimum value: 0, maximum value: 9999, default value: 100.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_INDEX_NUM_ENTRIES = 100\n\n# If the GENERATE_DOCSET tag is set to YES, additional index files will be\n# generated that can be used as input for Apple's Xcode 3 integrated development\n# environment (see:\n# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To\n# create a documentation set, doxygen will generate a Makefile in the HTML\n# output directory. Running make will produce the docset in that directory and\n# running make install will install the docset in\n# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at\n# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy\n# genXcode/_index.html for more information.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_DOCSET = NO\n\n# This tag determines the name of the docset feed. A documentation feed provides\n# an umbrella under which multiple documentation sets from a single provider\n# (such as a company or product suite) can be grouped.\n# The default value is: Doxygen generated docs.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_FEEDNAME = \"Doxygen generated docs\"\n\n# This tag determines the URL of the docset feed. A documentation feed provides\n# an umbrella under which multiple documentation sets from a single provider\n# (such as a company or product suite) can be grouped.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_FEEDURL =\n\n# This tag specifies a string that should uniquely identify the documentation\n# set bundle. This should be a reverse domain-name style string, e.g.\n# com.mycompany.MyDocSet. Doxygen will append .docset to the name.\n# The default value is: org.doxygen.Project.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_BUNDLE_ID = org.doxygen.Project\n\n# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify\n# the documentation publisher. This should be a reverse domain-name style\n# string, e.g. com.mycompany.MyDocSet.documentation.\n# The default value is: org.doxygen.Publisher.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_PUBLISHER_ID = org.doxygen.Publisher\n\n# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.\n# The default value is: Publisher.\n# This tag requires that the tag GENERATE_DOCSET is set to YES.\n\nDOCSET_PUBLISHER_NAME = Publisher\n\n# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three\n# additional HTML index files: index.hhp, index.hhc, and index.hhk. The\n# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop\n# on Windows. In the beginning of 2021 Microsoft took the original page, with\n# a.o. the download links, offline the HTML help workshop was already many years\n# in maintenance mode). You can download the HTML help workshop from the web\n# archives at Installation executable (see:\n# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo\n# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).\n#\n# The HTML Help Workshop contains a compiler that can convert all HTML output\n# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML\n# files are now used as the Windows 98 help format, and will replace the old\n# Windows help format (.hlp) on all Windows platforms in the future. Compressed\n# HTML files also contain an index, a table of contents, and you can search for\n# words in the documentation. The HTML workshop also contains a viewer for\n# compressed HTML files.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_HTMLHELP = NO\n\n# The CHM_FILE tag can be used to specify the file name of the resulting .chm\n# file. You can add a path in front of the file if the result should not be\n# written to the html output directory.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nCHM_FILE =\n\n# The HHC_LOCATION tag can be used to specify the location (absolute path\n# including file name) of the HTML help compiler (hhc.exe). If non-empty,\n# doxygen will try to run the HTML help compiler on the generated index.hhp.\n# The file has to be specified with full path.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nHHC_LOCATION =\n\n# The GENERATE_CHI flag controls if a separate .chi index file is generated\n# (YES) or that it should be included in the main .chm file (NO).\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nGENERATE_CHI = NO\n\n# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)\n# and project file content.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nCHM_INDEX_ENCODING =\n\n# The BINARY_TOC flag controls whether a binary table of contents is generated\n# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it\n# enables the Previous and Next buttons.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nBINARY_TOC = NO\n\n# The TOC_EXPAND flag can be set to YES to add extra items for group members to\n# the table of contents of the HTML help documentation and to the tree view.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTMLHELP is set to YES.\n\nTOC_EXPAND = NO\n\n# The SITEMAP_URL tag is used to specify the full URL of the place where the\n# generated documentation will be placed on the server by the user during the\n# deployment of the documentation. The generated sitemap is called sitemap.xml\n# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL\n# is specified no sitemap is generated. For information about the sitemap\n# protocol see https://www.sitemaps.org\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nSITEMAP_URL =\n\n# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and\n# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that\n# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help\n# (.qch) of the generated HTML documentation.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_QHP = NO\n\n# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify\n# the file name of the resulting .qch file. The path specified is relative to\n# the HTML output folder.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQCH_FILE =\n\n# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help\n# Project output. For more information please see Qt Help Project / Namespace\n# (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).\n# The default value is: org.doxygen.Project.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_NAMESPACE = org.doxygen.Project\n\n# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt\n# Help Project output. For more information please see Qt Help Project / Virtual\n# Folders (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).\n# The default value is: doc.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_VIRTUAL_FOLDER = doc\n\n# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom\n# filter to add. For more information please see Qt Help Project / Custom\n# Filters (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_CUST_FILTER_NAME =\n\n# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the\n# custom filter to add. For more information please see Qt Help Project / Custom\n# Filters (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_CUST_FILTER_ATTRS =\n\n# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this\n# project's filter section matches. Qt Help Project / Filter Attributes (see:\n# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHP_SECT_FILTER_ATTRS =\n\n# The QHG_LOCATION tag can be used to specify the location (absolute path\n# including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to\n# run qhelpgenerator on the generated .qhp file.\n# This tag requires that the tag GENERATE_QHP is set to YES.\n\nQHG_LOCATION =\n\n# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be\n# generated, together with the HTML files, they form an Eclipse help plugin. To\n# install this plugin and make it available under the help contents menu in\n# Eclipse, the contents of the directory containing the HTML and XML files needs\n# to be copied into the plugins directory of eclipse. The name of the directory\n# within the plugins directory should be the same as the ECLIPSE_DOC_ID value.\n# After copying Eclipse needs to be restarted before the help appears.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_ECLIPSEHELP = NO\n\n# A unique identifier for the Eclipse help plugin. When installing the plugin\n# the directory name containing the HTML and XML files should also have this\n# name. Each documentation set should have its own identifier.\n# The default value is: org.doxygen.Project.\n# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.\n\nECLIPSE_DOC_ID = org.doxygen.Project\n\n# If you want full control over the layout of the generated HTML pages it might\n# be necessary to disable the index and replace it with your own. The\n# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top\n# of each HTML page. A value of NO enables the index and the value YES disables\n# it. Since the tabs in the index contain the same information as the navigation\n# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nDISABLE_INDEX = YES\n\n# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index\n# structure should be generated to display hierarchical information. If the tag\n# value is set to YES, a side panel will be generated containing a tree-like\n# index structure (just like the one that is generated for HTML Help). For this\n# to work a browser that supports JavaScript, DHTML, CSS and frames is required\n# (i.e. any modern browser). Windows users are probably better off using the\n# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can\n# further fine tune the look of the index (see \"Fine-tuning the output\"). As an\n# example, the default style sheet generated by doxygen has an example that\n# shows how to put an image at the root of the tree instead of the PROJECT_NAME.\n# Since the tree basically has the same information as the tab index, you could\n# consider setting DISABLE_INDEX to YES when enabling this option.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nGENERATE_TREEVIEW = YES\n\n# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the\n# FULL_SIDEBAR option determines if the side bar is limited to only the treeview\n# area (value NO) or if it should extend to the full height of the window (value\n# YES). Setting this to YES gives a layout similar to\n# https://docs.readthedocs.io with more room for contents, but less room for the\n# project logo, title, and description. If either GENERATE_TREEVIEW or\n# DISABLE_INDEX is set to NO, this option has no effect.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nFULL_SIDEBAR = NO\n\n# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that\n# doxygen will group on one line in the generated HTML documentation.\n#\n# Note that a value of 0 will completely suppress the enum values from appearing\n# in the overview section.\n# Minimum value: 0, maximum value: 20, default value: 4.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nENUM_VALUES_PER_LINE = 4\n\n# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used\n# to set the initial width (in pixels) of the frame in which the tree is shown.\n# Minimum value: 0, maximum value: 1500, default value: 250.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nTREEVIEW_WIDTH = 180\n\n# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to\n# external symbols imported via tag files in a separate window.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nEXT_LINKS_IN_WINDOW = NO\n\n# If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email\n# addresses.\n# The default value is: YES.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nOBFUSCATE_EMAILS = YES\n\n# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg\n# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see\n# https://inkscape.org) to generate formulas as SVG images instead of PNGs for\n# the HTML output. These images will generally look nicer at scaled resolutions.\n# Possible values are: png (the default) and svg (looks nicer but requires the\n# pdf2svg or inkscape tool).\n# The default value is: png.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nHTML_FORMULA_FORMAT = png\n\n# Use this tag to change the font size of LaTeX formulas included as images in\n# the HTML documentation. When you change the font size after a successful\n# doxygen run you need to manually remove any form_*.png images from the HTML\n# output directory to force them to be regenerated.\n# Minimum value: 8, maximum value: 50, default value: 10.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nFORMULA_FONTSIZE = 10\n\n# The FORMULA_MACROFILE can contain LaTeX \\newcommand and \\renewcommand commands\n# to create new LaTeX commands to be used in formulas as building blocks. See\n# the section \"Including formulas\" for details.\n\nFORMULA_MACROFILE =\n\n# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see\n# https://www.mathjax.org) which uses client side JavaScript for the rendering\n# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX\n# installed or if you want to formulas look prettier in the HTML output. When\n# enabled you may also need to install MathJax separately and configure the path\n# to it using the MATHJAX_RELPATH option.\n# The default value is: NO.\n# This tag requires that the tag GENERATE_HTML is set to YES.\n\nUSE_MATHJAX = NO\n\n# With MATHJAX_VERSION it is possible to specify the MathJax version to be used.\n# Note that the different versions of MathJax have different requirements with\n# regards to the different settings, so it is possible that also other MathJax\n# settings have to be changed when switching between the different MathJax\n# versions.\n# Possible values are: MathJax_2 and MathJax_3.\n# The default value is: MathJax_2.\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_VERSION = MathJax_2\n\n# When MathJax is enabled you can set the default output format to be used for\n# the MathJax output. For more details about the output format see MathJax\n# version 2 (see:\n# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3\n# (see:\n# http://docs.mathjax.org/en/latest/web/components/output.html).\n# Possible values are: HTML-CSS (which is slower, but has the best\n# compatibility. This is the name for Mathjax version 2, for MathJax version 3\n# this will be translated into chtml), NativeMML (i.e. MathML. Only supported\n# for MathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This\n# is the name for Mathjax version 3, for MathJax version 2 this will be\n# translated into HTML-CSS) and SVG.\n# The default value is: HTML-CSS.\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_FORMAT = HTML-CSS\n\n# When MathJax is enabled you need to specify the location relative to the HTML\n# output directory using the MATHJAX_RELPATH option. The destination directory\n# should contain the MathJax.js script. For instance, if the mathjax directory\n# is located at the same level as the HTML output directory, then\n# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax\n# Content Delivery Network so you can quickly see the result without installing\n# MathJax. However, it is strongly recommended to install a local copy of\n# MathJax from https://www.mathjax.org before deployment. The default value is:\n# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2\n# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest\n\n# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax\n# extension names that should be enabled during MathJax rendering. For example\n# for MathJax version 2 (see\n# https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):\n# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols\n# For example for MathJax version 3 (see\n# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html):\n# MATHJAX_EXTENSIONS = ams\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_EXTENSIONS =\n\n# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces\n# of code that will be used on startup of the MathJax code. See the MathJax site\n# (see:\n# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an\n# example see the documentation.\n# This tag requires that the tag USE_MATHJAX is set to YES.\n\nMATHJAX_CODEFILE =\n\n# When the SEARCHENGINE tag is enabled doxygen will generate a search box for\n# the HTML output. The underlying search engine uses javascript and DHTML and\n# should work on any modern browser. Note that when using HTML help\n# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)\n# there is already a search function so this one should typically be disabled.\n# For large projects the javascript based search engine can be slow, then\n# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to\n# search using the keyboard; to jump to the search box use + S\n# (what the is depends on the OS and browser, but it is typically\n# , /