-
Notifications
You must be signed in to change notification settings - Fork 13.5k
clang-15: crash on va_arg (arm) #58794
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
there are multiple reports referring to this assertion: https://github.com/llvm/llvm-project/search?q=getCommonPtr&type=issues. could someone please prioritize and fix it? |
@llvm/issue-subscribers-clang-codegen |
I try to fix this issue in https://reviews.llvm.org/D138137 |
@llvm/issue-subscribers-backend-arm |
…e variadic arg Fix ARMABIInfo::EmitVAAarg crash with empty record type variadic arg Open issue: #58794 Reviewed By: rjmccall Differential Revision: https://reviews.llvm.org/D138137
/cherry-pick 80f4446 |
Failed to cherry-pick: 80f4446 https://github.com/llvm/llvm-project/actions/runs/3504147547 Please manually backport the fix and push it to your github fork. Once this is done, please add a comment like this:
|
/cherry-pick 80f4446 |
/branch llvm/llvm-project-release-prs/issue58794 |
…e variadic arg Fix ARMABIInfo::EmitVAAarg crash with empty record type variadic arg Open issue: llvm/llvm-project#58794 Reviewed By: rjmccall Differential Revision: https://reviews.llvm.org/D138137 (cherry picked from commit 80f4446)
/pull-request llvm/llvm-project-release-prs#218 |
we have used Phab for these kinds of fixes as well so far. Not sure if we want to make exceptions based on paths. I am fine with that fix to be committed directly though. WDYT @tstellar ? |
I normally file a new bug for backporting to make it easier too. |
doesn't make any sense to use phab for github actions stuff.. since you can't test what you are reviewing. one wrong whitespace and you need to revert and then start over.. |
I think it's a bigger decision to enable it for anything than just something we can decide here. I usually test the actions in a personal fork before submitting. |
Phabricator is fine for these changes. You can always create a pull request against the llvm-project-release-prs repo for testing. |
/cherry-pick 80f4446 |
/branch llvm/llvm-project-release-prs/issue58794 |
…e variadic arg Fix ARMABIInfo::EmitVAAarg crash with empty record type variadic arg Open issue: llvm/llvm-project#58794 Reviewed By: rjmccall Differential Revision: https://reviews.llvm.org/D138137 (cherry picked from commit 80f4446)
…e variadic arg Fix ARMABIInfo::EmitVAAarg crash with empty record type variadic arg Open issue: llvm/llvm-project#58794 Reviewed By: rjmccall Differential Revision: https://reviews.llvm.org/D138137 (cherry picked from commit 80f4446)
Repro:
File:
x.c
command:
clang-15 -target arm-linux-gnu -shared -O2 x.c
underlying assertion:
clang: /root/llvm-project/clang/include/clang/AST/Type.h:753: const clang::ExtQualsTypeCommonBase* clang::QualType::getCommonPtr() const: Assertion `!isNull() && "Cannot retrieve a NULL type pointer"' failed.
stdout/stderr in production:
The text was updated successfully, but these errors were encountered: