Skip to content
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.

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

Resolution of local unit id in GlobMem #133

Merged
merged 4 commits into from
Nov 20, 2016
Merged

Conversation

fuchsto
Copy link
Member

@fuchsto fuchsto commented Nov 19, 2016

Fixes #125

@fmoessbauer
Copy link
Member

There are still some team all related functions like dash::size() or dash::myid() used. This leads to the problems described in #132.

@fmoessbauer fmoessbauer added this to the dash-0.3.0 milestone Nov 20, 2016
…25-globmem-myid

Conflicts:
	dash/include/dash/algorithm/Accumulate.h
	dash/include/dash/algorithm/Equal.h
	dash/include/dash/algorithm/Mismatch.h
@fmoessbauer fmoessbauer merged commit 2bf059f into development Nov 20, 2016
ddiefenthaler pushed a commit that referenced this pull request Nov 22, 2016
* added test case for team-aware array allocation

* removed explicit usage of unit id in array.lbegin

* added unit test for GlobMem lbegin using teams

* reverted changes from PR #133 as GlobMem requires absolute unit ids

* renamed unit id parameters in GlobMem to differentiate between realtive and global unit ids

* skip team unit tests if team is already splitted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants