Repository navigation
Conversation
| `libiomp` (Intel)** can cause crashes or deadlocks. Even querying the maximum | ||
| number of threads for a subsequent parallel region can trigger the problem. | ||
| The incompatibility has been observed on Linux and macOS, and a similar | ||
| deadlock was [reported on Windows](https://github.com/scipy/scipy/issues/23989). |
There was a problem hiding this comment.
Since this deadlock was discovered on Windows, I think the Linux-only condition to display the warning in _warn_if_incompatible_openmp should be removed and we should warn on all operating systems.
Do you agree @lucascolley?
@Yushu-Li would you be interested in trying to reproduce the failure on macOS and Windows to confirm? If so we should update the code in _warn_if_incompatible_openmp and update this paragraph accordingly.
There was a problem hiding this comment.
Since this deadlock was discovered on Windows, I think the Linux-only condition to display the warning in
_warn_if_incompatible_openmpshould be removed and we should warn on all operating systems.Do you agree @lucascolley?
yes, re-reading the linked issue, I think that was my thought at the time
The multiple-OpenMP guide linked from the runtime warning only discusses Linux and macOS. I added the Windows report linked in #204 and separated the scope of the runtime risk from the scope of the current Linux-only warning. On some Windows builds, a library can forward to the other runtime, so two filenames alone do not establish a conflict.
Refs #204. This changes the troubleshooting guide only. I checked the wording against the warning implementation and the linked SciPy report.
git diff --checkpassed and the API introspection tests reported 3 passed and 2 skipped on macOS. I did not reproduce the Windows deadlock locally.I used OpenAI Codex to assist with the documentation change and verification.