From c7925c3891d4bc9e14180bf2610e3e363d6e1241 Mon Sep 17 00:00:00 2001 From: David Longnecker Date: Wed, 17 Jun 2026 11:30:46 -0700 Subject: [PATCH] Adjust dlopen package docs to mention `CHPL_COMM=none` is supported Signed-off-by: David Longnecker --- modules/packages/DynamicLoading.chpl | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/modules/packages/DynamicLoading.chpl b/modules/packages/DynamicLoading.chpl index fda1d9e9bc8e..4765cfa47194 100644 --- a/modules/packages/DynamicLoading.chpl +++ b/modules/packages/DynamicLoading.chpl @@ -74,9 +74,10 @@ having all loaded Chapel programs utilize a single shared copy of the runtime. .. warning:: This feature is highly unstable (even more than the rest of this module). - As of the 2.9 release, it is only supported when ``CHPL_COMM=gasnet`` and - ``CHPL_LIB_PIC=pic``. Safety checks have not been added yet, so dynamically - loaded code may break in unexpected ways if these constraints are not met. + As of the 2.9 release, it is only supported when ``CHPL_COMM=none`` or + ``CHPL_COMM=gasnet``, and also requires ``CHPL_LIB_PIC=pic``. Safety checks + have not been added yet, so dynamically loaded code may break in unexpected + ways if these constraints are not met. Additionally, while it should be possible to execute parallel and distributed code from a loaded Chapel library, it is possible that certain