Dan Bonachea

Results 20 issues of Dan Bonachea

### Overview This PR enables GASNet-level shared-memory bypass communication for all GASNet conduits (in fast/large segment modes), which should notably greatly accelerate co-locale communication for `CHPL_COMM=gasnet CHPL_COMM_SUBSTRATE=ibv`. This fixes the...

Now that Chapel finally has a [high-quality Spack package](https://packages.spack.io/package.html?name=chapel), the next logical step is to pursue Chapel membership in the [E4S Programming Model SDK](https://e4s-project.github.io/DocPortal.html). [E4S](https://e4s-project.github.io/about.html) is a DOE ASCR product...

area: BTR
type: Portability

Currently Caffeine always crashes with obscure signals on shared memory exhaustion. Shared heap exhaustion is a very common failure mode in practice and probably the most important runtime error to...

priority=medium

This issue requests creation and maintenance of a git ref (branch or tag, don't really care which) that always points to the latest stable public release of Chapel. The existence...

area: BTR
user issue

The legacy GASNet-1 backend has been superseded by the new GASNet-EX backend, which has been Chapel's default GASNet backend since 658ac15b5 (Chapel 2.1). Both backends run over the same GASNet-EX...

Repair _some_ of the problems currently preventing use of this library with CCE 17.0.0. These changes are necessary, but not sufficient to pass `fpm test`. Specifically, test/test-intrinsic_array remains broken due...

This test has apparently been returning nonsense since the false-assertion example was renamed in 6f4ddfd. The test design (nested invocation of fpm) remains horribly fragile for multiple fundamental reasons, but...

This PR ensures that `#define ASSERTIONS 1` in source code is honored by the `call_assert` macros, regardless of the `ASSERTIONS` setting used to build `assert_m`

Currently the approach taken to unit testing `prif_stop` and `prif_error_stop` is to unconditionally invoke `./build/run-fpm.sh` in the `fpm` built Caffeine unit test, and inspecting the resulting process exit code. I...

These should basically just be a thin wrapper around integer atomics, ie: ```Fortran type, public :: prif_event_type private integer(PRIF_ATOMIC_INT_KIND) :: value = 0 end type ! Everything below is UNTESTED...

priority=medium