-
Notifications
You must be signed in to change notification settings - Fork 9
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
#1974: fix various c++17 deprecations and compile errors #1975
Conversation
Pipelines resultsPR tests (gcc-7, ubuntu, mpich, trace runtime, LB) Build for a4212f8
PR tests (gcc-8, ubuntu, mpich, address sanitizer) Build for 2375eda
PR tests (clang-5.0, ubuntu, mpich) Build for 2375eda
PR tests (clang-3.9, ubuntu, mpich) Build for 2375eda
PR tests (nvidia cuda 10.1, ubuntu, mpich) Build for 2375eda
PR tests (nvidia cuda 11.0, ubuntu, mpich) Build for 2375eda
PR tests (gcc-6, ubuntu, mpich) Build for 2375eda
PR tests (clang-11, ubuntu, mpich) Build for a4212f8
PR tests (clang-10, ubuntu, mpich) Build for a4212f8
PR tests (gcc-11, ubuntu, mpich, json schema test) Build for a4212f8
PR tests (gcc-12, ubuntu, mpich) Build for a4212f8
PR tests (intel icpc, ubuntu, mpich) Build for a4212f8
PR tests (gcc-10, ubuntu, openmpi, no LB) Build for 2375eda
PR tests (intel icpx, ubuntu, mpich) Build for a4212f8
PR tests (clang-9, ubuntu, mpich) Build for a4212f8
PR tests (gcc-5, ubuntu, mpich) Build for 2375eda
PR tests (gcc-9, ubuntu, mpich, zoltan) Build for 2375eda
|
Lol at those compiler errors |
🤦 maybe I should have tested with C++14.... well I guess I'm going to have to find another way. Maybe the least gross way will be to just do explicit capture for everything, no default capture |
Or wait a bit, and we can fold in "require C++17" with the changes to adapt to it. EMPIRE will be able to accept that in the next few weeks, BVH is already there as I understand it, and I can check on our other app. |
Yeah that is my bad, I was getting the C++20 flag from Kokkos. I forgot implicit this is deprecated in 20, not 17. I'll remove it from the PR |
Incidentally, you're "I'll revert that" are a good argument for committing distinct changes separately - it would be really easy to just rebase to put the We'll want to figure out how to write code that's happy compiled as C++17 or C++20 starting once we require 17. |
a4212f8
to
2375eda
Compare
Split into two commits, made a third one for implicit |
This PR is broken because our checking scripts don't allow '+' in the name of the branch. New PR: #1978 |
Fixes #1974