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

Kokkos::Timer #234

Closed
hcedwar opened this issue Mar 31, 2016 · 4 comments
Closed

Kokkos::Timer #234

hcedwar opened this issue Mar 31, 2016 · 4 comments
Assignees
Labels
Feature Request Create new capability; will potentially require voting
Milestone

Comments

@hcedwar
Copy link
Contributor

hcedwar commented Mar 31, 2016

"Expose" and commit to supporting the Kokkos timer by making it available in the Kokkos namespace.
Review interface and implementation prior to this update.

@hcedwar hcedwar added the Feature Request Create new capability; will potentially require voting label Mar 31, 2016
@hcedwar hcedwar added this to the Spring 2016 milestone Mar 31, 2016
@crtrott
Copy link
Member

crtrott commented Mar 31, 2016

We should probably make it use std::chrono features internally.

@dsunder
Copy link
Contributor

dsunder commented Mar 31, 2016

Here is the simple timer that I created for Uintah using c++11.

—Dan

On Mar 31, 2016, at 12:08 PM, Christian Trott notifications@github.com wrote:

We should probably make it use std::chrono features internally.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #234 (comment)

@bartlettroscoe
Copy link
Contributor

Related to trilinos/Trilinos#253.

@ndellingwood
Copy link
Contributor

Pull request issued #274

Timer available in Kokkos namespace.

Updated unit tests, performance tests, and examples using
Kokkos::Impl::Timer to use Kokkos::Timer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Create new capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

5 participants