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

[HIP] enable global lock arrays #3418

Merged
merged 5 commits into from
Sep 25, 2020
Merged

[HIP] enable global lock arrays #3418

merged 5 commits into from
Sep 25, 2020

Conversation

Rombur
Copy link
Member

@Rombur Rombur commented Sep 24, 2020

This PR enables:

  • the global lock arrays
  • all the incremental tests
  • more tests of the testsuite. Some are modified to reduce the size of the loop.

As far as I can tell the tests that still do not pass are tests that either use complex or tests which pass for smaller sizes.

Copy link
Contributor

@masterleinad masterleinad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good if you could provide comments on why these tests still fail in case you know.

@@ -326,8 +326,6 @@ if(Kokkos_ENABLE_HIP)
# FIXME_HIP
LIST(REMOVE_ITEM HIP_SOURCES
hip/TestHIP_AtomicOperations_complexdouble.cpp
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the problem with this test?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't really investigate the problem with complex numbers yet.

@@ -121,12 +121,21 @@ void test_team_policy_max_recommended_static_size(int scratch_size) {
.set_scratch_size(0, Kokkos::PerTeam(scratch_size)),
FunctorFor<T, N, PolicyType, S>());
MyArray<T, N> val;
double n_leagues = 10000;
// FIXME_HIP
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any idea what the issue here is?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the segfault that we reported to AMD and we talked about during the last group meeting

@@ -477,8 +477,11 @@ bool Test(int test) {
test_scalar<long long int, ExecutionSpace>(317, team_size, test);
passed = passed && test_scalar<float, ExecutionSpace>(317, team_size, test);
passed = passed && test_scalar<double, ExecutionSpace>(317, team_size, test);
// FIXME_HIP
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... and here?

Copy link
Member

@crtrott crtrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you open an explicit issue to track the complex number issue? Otherwise is ok.

@Rombur
Copy link
Member Author

Rombur commented Sep 24, 2020

I have open an issue

@Rombur
Copy link
Member Author

Rombur commented Sep 24, 2020

Retest this please

@dalg24 dalg24 merged commit 1fe6f1b into kokkos:develop Sep 25, 2020
@Rombur Rombur deleted the hip_tests branch April 7, 2022 14:45
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.

None yet

4 participants