Chapel-GASNet
Chapel-GASNet is a Docker image providing a Chapel high-performance programming environment preconfigured with the GASNet communication layer, enabling…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
56/100 Fair
- Maintained
- 100last commit 22 days ago
- Popular
- 209 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 404 GB minimum RAM, runs on ARM
- GitHub stars
- 9
- Open issues
- 5
- Last commit
- 2026-10-30
- Latest release
- gex-2025.8.0
- Activity
- declining
Checked 18 days ago - source: GitHub (BerkeleyLab/gasnet)
Resources & Compatibility
Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Running multilocale Chapel binaries Compiling a program with chpl produces two binaries (for example hello_real as well as hello); when you run the program you must pass the -nl <n> command-line argument to set the number of locales to start. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which GASNet API became the default in Chapel?
Chapel switched to using the GASNet EX API as the default. Related GASNet test scripts were also updated.
What should Chapel-GASNet Dockerfiles set to avoid --specialize warnings when compiling with --fast?
They should explicitly set CHPL_TARGET_CPU. Missing that setting caused --specialize warnings when compiling with --fast.
How do you select the GASNet communication layer in Chapel?
Set CHPL_COMM_SUBSTRATE to indicate the GASNet substrate.
What runtime error was reported after moving to Chapel 1.19 with GASNet PSM on OmniPath?
Users reported randomly receiving ERROR calling: gasnet_barrier_try (id, 0). This happened after changing to version 1.19 while using the OmniPath implementation.
What Homebrew gotcha can Chapel-GASNet trigger?
GASNet can save a Homebrew shim. That can cause Homebrew audit issues.
Answers sourced from chapel-lang.org, chapel.discourse.group, chapel.discourse.group, chapel.discourse.group, stackoverflow.com
Community
- [Chapel Merge] Avoid homebrew issues with gasnet saving homebrew shim (forum)
- [Chapel Merge] Switch to using the GASNet EX API as the default (forum)
- New Issue: [Bug]: Building GASNet with GCC inside homebrew formula ... (forum)
- New Issue: [Bug]: Dockerfiles for GASNet should use CHPL_TARGET_CPU ... (forum)
Collected 48 days ago - public community threads