Skip to content

Adjust dlopen package docs to mention CHPL_COMM=none is supported #28989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dlongnecke-cray wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −3
Open

Adjust dlopen package docs to mention CHPL_COMM=none is supported #28989

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions modules/packages/DynamicLoading.chpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down