-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
expansion pattern 'CompatibleObjectType' contains no argument packs, with CUDA 10 #1347
Comments
Thanks for reporting! I have not seen this before, but maybe someone has an idea. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have the same issue with nvcc 10.0, compile with -std=c+=11 |
Same issue with CUDA 10.1 with std=c++14 |
Also running into this problem with CUDA 10.1 and c++ 11 |
I've run into the same problem with CUDA 10.1, g++ 6.4.0, c++11. |
Having the same issue here. It's possible that this is related to a bug similar to this: I'm not entirely sure what c compiler NVCC uses or if they have their own and have the same bug. I was able to work around this issue by not putting any json.hpp code into .cu files. The project I'm working with uses VS to compile the cpp files and NVCC to compile the .cu files so perhaps this isn't feasible for everyone else. I was also able to get around this by commenting out a lot of the vector/string code in the json.hpp header but then of course you can't read either data type, which wasn't workable for me. |
I'm also have the same problem for the latest version, but it does work with CUDA 10.1 when I use version 3.2.0 of this JSON library (so newer than version 2.1 from the OP). |
Hi,
I'm using your JSON library in my code. I have a pretty old version (2.1) and would like to upgrade to 3.4.0. However the CUDA 10 compiler seems to have errors when trying to get data as a vectors. With the GCC compiler (5.4) it compiles fine.
I attach example code from this issue, where the issue was solved:
This gives the following compilation errors:
Using the
get<std::vector<std::string>>
method gives even more errors on top of the previous ones.Have you seen this error before?
Thanks!
The text was updated successfully, but these errors were encountered: