-
Notifications
You must be signed in to change notification settings - Fork 798
[CI] Run Nightly E2E CI in pre-C++11 ABI mode #16235
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
Conversation
We expect that our runtime library should work with user code compiled either way, but we don't be running double amount of testing in pre-commit/post-commit CI to verify that. Nightly looks like a reasonable choice to test this.
|
I'm doing a test run at https://github.com/intel/llvm/actions/runs/12126461497 to ensure everything would pass. https://github.com/intel/llvm/actions/runs/12126279223 (it had extra changes to speed up testing and enable verbose output) verified that the option is passed properly. |
|
Just curious... SYCL requires at least C++17. What is the use-case for such an antique atrocity? 🤔 |
Even modern g++ in modern c++ modes support that. As for the reason, PyTorch, IIUC. |
This is an updated version of intel#16179. Run-time ABI mismatch resulting in a segmentation fault was uncovered why enabling extra testing in intel#16235, this updated version fixes that.
|
There were fixes in |
We expect that our runtime library should work with user code compiled either way, but we don't be running double amount of testing in pre-commit/post-commit CI to verify that. Nightly looks like a reasonable choice to test this.