-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix performance for CUDA 9.2 / 10.0 #1281
Conversation
do perftest |
do perftest |
do perftest |
do perftest |
do perftest |
do perftest |
1 similar comment
do perftest |
53289fa
to
66cc615
Compare
do perftest |
do perftest |
1 similar comment
do perftest |
launch strgrid |
launch icgrid |
do perftest |
launch strgrid |
launch icgrid |
do perftest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove formating changes in meta
from this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new usages of std::move
/std::forward
are arrived with the recent Hannes PR. Please fix them as well.
launch strgrid |
launch icgrid |
do perftest |
…s into no_constexpr_on_device
do perftest |
- make constexpr compiler dependent whenever possible (replace with macro `GT_CONSTEXPR`) - remove `const_expr::move` and `const_expr::forward` - add `wstd::move` and `wstd::forward` (move and forward are only constexpr if compiler does not suffer from it)
- make constexpr compiler dependent whenever possible (replace with macro `GT_CONSTEXPR`) - remove `const_expr::move` and `const_expr::forward` - add `wstd::move` and `wstd::forward` (move and forward are only constexpr if compiler does not suffer from it)
GT_CONSTEXPR
)const_expr::move
andconst_expr::forward
wstd::move
andwstd::forward
(move and forward are only constexpr if compiler does not suffer from it)