Joseph Schuchart
Joseph Schuchart
According to the discussion on https://github.com/open-mpi/ompi/pull/10349, the `ompi_info_t` is a) an `opal_object_t` and can thus be allocated using `OBJ_NEW`, but b) must (in the general case) be allocated using `ompi_info_allocate`...
[//]: # " If the issue is connected to existing Uncrustify options please, if possible, add the" [//]: # " following information to ease up the process:" [//]: # "...
We need to call into MPI every once in a while as otherwise polling on a local variable may not trigger progress if that is needed.
Make the team hierarchy a tree and allow for cloning teams, which is useful in multi-threaded environments. Fixes #658
The assert in the following example fails for some `{x,y}`: ``` using PatternT = typename dash::TilePattern; using TiledMatrix = dash::Matrix; TiledMatrix A(num_blocks, num_blocks, // super-blocks dash::TILE(super_block_size), dash::TILE(super_block_size), block_size, block_size, dash::TILE(block_size),...
Can someone please shed some light on the following issue? I have a 2D NArray with TilePattern and use `global_at` to determine the global offsets of elements in the tiles....
A thing I noticed (again) while looking at #504: All of the DASH reference types are `container_compatible`, i.e., `dash::GlobIter`, `dash::GlobRef`, and `dash::GlobPtr`. However, internally all but `dash::GlobRef` contain local pointers...
This PR changes the build scripts and CMakeList to configure DART to use regular windows instead of dynamic + shared memory windows in `dart_team_memalloc_aligned`. Background: The use of dynamic windows...