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.

Sign up for GitHub

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

Jump to bottom

MemoryPool fails to compile on non-cuda non-x86 #297

Closed
crtrott opened this issue May 24, 2016 · 1 comment
Closed

MemoryPool fails to compile on non-cuda non-x86 #297

crtrott opened this issue May 24, 2016 · 1 comment
Assignees
@crtrott
Labels
Bug Broken / incorrect code; it could be Kokkos' responsibility, or others’ (e.g., Trilinos)
Milestone
Spring 2016

Comments

@crtrott
Copy link
Member

crtrott commented May 24, 2016

There is a #error unknown architecture.
@crtrott crtrott added the Bug Broken / incorrect code; it could be Kokkos' responsibility, or others’ (e.g., Trilinos) label May 24, 2016
@crtrott crtrott added this to the Spring 2016 milestone May 24, 2016
@crtrott
Copy link
Member Author

crtrott commented May 24, 2016 •
edited

Trying to use:

std::chrono::high_resolution_clock::now().time_since_epoch().count();

now as fallback

crtrott added a commit that referenced this issue May 24, 2016
@crtrott
MemoryPool: use choro high resolution clock as fallback for clock.
0781321 
This makes the thing pass on Power8 and addresses issue #297.
@crtrott crtrott self-assigned this May 24, 2016
@crtrott crtrott closed this as completed May 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@crtrott crtrott

Labels
Bug Broken / incorrect code; it could be Kokkos' responsibility, or others’ (e.g., Trilinos)
Projects
None yet
Milestone
Spring 2016
Development

No branches or pull requests
1 participant
@crtrott