-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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][ASTImporter] clang/lib/AST/Decl.cpp:1605: clang::LinkageInfo clang::LinkageComputer::getLVForDecl(const clang::NamedDecl *, clang::LVComputationKind): Assertion `!Old || Old->getCachedLinkage() == D->getCachedLinkage()' failed. #65913
Comments
@llvm/issue-subscribers-clang-frontend
`clang/lib/AST/Decl.cpp:1605: clang::LinkageInfo clang::LinkageComputer::getLVForDecl(const clang::NamedDecl *, clang::LVComputationKind): Assertion '!Old || Old->getCachedLinkage() == D->getCachedLinkage()' failed.`
when importing the following
```
template struct B {
template friend void f(const B&, const B&) {}
};
template struct A : public B {
friend void f(const A&, const A&) {}
};
template struct O { namespace { struct I {}; } namespace NS { typedef O::M MT2;
template struct B {
ASTTests: /home/xxxxx/Sources/llvm-project-main/clang/lib/AST/Decl.cpp:1605: clang::LinkageInfo clang::LinkageComputer::getLVForDecl(const clang::NamedDecl , clang::LVComputationKind): Assertion `!Old || Old->getCachedLinkage() == D->getCachedLinkage()' failed.
|
…ence on recordType (#76226) Types comparison in `StructuralEquivalence` ignores its `DeclContext` when they are generated by template specialization implicitly and this will produce incorrect result. Add comparison of `DeclContext` of ClassTemplateSpecializationDecl to improve result. fix [issue](#65913) Co-authored-by: huqizhi <836744285@qq.com>
clang/lib/AST/Decl.cpp:1605: clang::LinkageInfo clang::LinkageComputer::getLVForDecl(const clang::NamedDecl *, clang::LVComputationKind): Assertion '!Old || Old->getCachedLinkage() == D->getCachedLinkage()' failed.
when importing the following
into
Stack:
The text was updated successfully, but these errors were encountered: