-
Notifications
You must be signed in to change notification settings - Fork 156
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
Remote-MQPU to support C++-17 standard #1111
Comments
What is the error? |
I believe you can search our codebase for I wonder if it's possible that it's also just missing the |
The linked one [Ed: all of them] has a Still would be good to know what the failure mode actually is. |
I just checked. 3 tests pass when setting the appropriate --std=c++17 flag, the the failures for the others are the following: These all run into the same issue, which looks related to serialization/deserialization (@1tnguyen I though we didn't have a new dependency there, do we?):
The async functions run into an error due to a lack of suitable copy constructor for a tuple version that it seems to be picking up from the system:
(same error if I add a gcc-11 toolchain installation, just now for the tuple implementation from there) |
Possibly related: #1281 |
Currently,
--target remote-mqpu
does not work with C++-17 standard.We need to add C++17 support for this target.
The text was updated successfully, but these errors were encountered: