-
Notifications
You must be signed in to change notification settings - Fork 13.4k
[clang] Assertion `Eval.Val.hasValue()' failed. #119125
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: Yihan Yang (yijan4845)
**This testcase is generated by a fuzzer.**
Compiler Explorer: https://godbolt.org/z/zhK3Eddqs This valid code will crash on clang assertion trunk: template<typename T>
struct B {
[[clang::annotate("test", (9, (void)T{}))]] void t() {}
};
B<int> b;
This goes back to clang-12. Stack dump:
|
This is #105789 |
Oops, that's a PR, not an open issue. :-) |
@yijan4845 I am not sure how to reach out to you but I was wondering do you have any papers on your fuzzing approach? It seems to do a decent job of finding regressions. It would be great to know what is different about your approach that helps it find recent regressions so well. |
We are designing and synthesizing mutators specifically tailored for LLVM, utilizing programs extracted from unit tests as seed inputs. We will release our paper and code soon. Stay in touch! |
Evaluating the attribute expression can be successful without resulting in a value. Namely, when the expression is of type void. Fixes #119125
… (#105789) Evaluating the attribute expression can be successful without resulting in a value. Namely, when the expression is of type void. Fixes llvm/llvm-project#119125
Evaluating the attribute expression can be successful without resulting in a value. Namely, when the expression is of type void. Fixes llvm#119125
This testcase is generated by a fuzzer.
Compiler Explorer: https://godbolt.org/z/zhK3Eddqs
This valid code will crash on clang assertion trunk:
This goes back to clang-12.
Stack dump:
The text was updated successfully, but these errors were encountered: