-
Notifications
You must be signed in to change notification settings - Fork 11.9k
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
[clang] Assertion `!KnownValid && "Explicit template arguments?"' failed. #113602
Comments
@llvm/issue-subscribers-clang-frontend Author: Yihan Yang (yijan4845)
**This testcase is generated by a fuzzer.**
Compiler Explorer: https://godbolt.org/z/G5nn9vcWz This invalid code will crash on Clang Assertion Trunk. template <typename T> float nosplit();
template <typename T> int nosplit();
int nosplit() {
return nosplxt<int>();
} It seems that this goes back to clang-9. This case can be triggered only when Stack dump:
|
This assertion occurs because recovery proceeds with llvm-project/clang/lib/Sema/SemaExpr.cpp Lines 2540 to 2550 in fcfd643
llvm-project/clang/lib/Sema/SemaExpr.cpp Line 2562 in fcfd643
and llvm-project/clang/lib/Sema/SemaExpr.cpp Lines 2551 to 2561 in fcfd643
@AaronBallman @erichkeane @cor3ntin @Sirraide should recovery be disallowed in such cases (when llvm-project/clang/lib/Sema/SemaExpr.cpp Lines 2576 to 2577 in fcfd643
Alternatively, should llvm-project/clang/lib/Sema/SemaExpr.cpp Line 2551 in fcfd643
/ llvm-project/clang/lib/Sema/SemaExpr.cpp Lines 2524 to 2526 in fcfd643
be updated to more precisely select the best candidate by prioritizing those with the correct type? |
This testcase is generated by a fuzzer.
Compiler Explorer: https://godbolt.org/z/G5nn9vcWz
This invalid code will crash on Clang Assertion Trunk.
It seems that this goes back to clang-9. This case can be triggered only when
did you mean 'nosplit'?
emitted by the compiler.Stack dump:
The text was updated successfully, but these errors were encountered: