-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Ambiguous Template Specialization with Xtensor #91504
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
Comments
@llvm/issue-subscribers-clang-frontend Author: John Tramm (jtramm)
Sometime in the last month and a half or so, LLVM has broken for the C++ xtensor header library (https://github.com/xtensor-stack/xtensor).
I have a minimal reproducer, #include "xtensor/xarray.hpp"
int main(void) {
xt::xarray<double> temp;
return 0;
} compiled as:
It works fine with llvm 18.1.0, and up to 1c683eb, but was broken somewhere between 1c683eb and 05f4448. With the current develop version of LLVM, it gives the following error:
|
I've been encountering this issue as well. I've done some bisecting, and I think the breaking commit is b86e099. |
Already reported, see here: #89807 (comment) Xtensor already includes workaround for template-template-args changes, but it tests for it in GCC specific way, instead of using standard feature testing macros. |
See issues: - llvm/llvm-project#91504 - xtensor-stack/xtensor#2783
Fixed by #91833 |
Sometime in the last month and a half or so, LLVM has broken for the C++ xtensor header library (https://github.com/xtensor-stack/xtensor).
I have a minimal reproducer,
main.cpp
:compiled as:
It works fine with llvm 18.1.0, and up to 1c683eb, but was broken somewhere between 1c683eb and 05f4448.
With the current develop version of LLVM, it gives the following error:
The text was updated successfully, but these errors were encountered: