Add libomp/libiomp compatibility experiment scripts#14
Closed
ogrisel wants to merge 1 commit into
Closed
Conversation
Scripts to reproduce and test the Linux-specific incompatibility between Intel OpenMP (libiomp) and LLVM OpenMP (libomp) with recent library versions. Supports follow-up investigation from PR joblib#222. Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds reproducible experiment scripts for follow-up investigation from PR joblib#222 about whether the Linux
libiomp+libompwarning is still needed with recent library versions.Findings (Linux, Jul 2026)
Tested with intel-openmp 2025.0.0 (libiomp perf lib 5.0.20240820) and LLVM libomp 18.1.8 (Clang 18.1 build), matching the
pylatest_conda_mkl_clang_gccCI setup.The warning is still needed on Linux. Recent versions remain incompatible:
omp_get_max_threadsfrom both runtimesthreadpool_limits()after nested prange+BLASKMP_DUPLICATE_LIB_OK=TRUELoading both libraries without calling into both simultaneously can appear fine; active use of both OpenMP APIs still crashes or deadlocks.
Scripts
experiments/libomp_libiomp_repro.c— minimal C reproducer (LLVM bug #43565)experiments/libomp_libiomp_variants.c— load-only / intel-first / llvm-first variantsexperiments/run_experiments.py— Python integration tests mirroring threadpoolctl usageHow to run
Recommendation
Keep the Linux-only warning from PR joblib#222. Do not remove the warning on any platform without new evidence that the runtimes have become compatible.