-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[modules] Handle friend function that was a definition but became only a declaration during AST deserialization #132214
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
91e057b
[clang] Fix for regression #130917
dmpolukhin adf6dfd
Add test case with C++ modules
dmpolukhin a564da2
Add flag to FunctionDecl
dmpolukhin 2b42b4d
Fix formatting
dmpolukhin 8d5ecfd
Add missing initialization
dmpolukhin df9fd8b
Move ThisDeclarationWasADefinition to ExternalASTSource
dmpolukhin d7234be
Rename + add only friend functions to the map
dmpolukhin 94efa55
Move ThisDeclarationWasADefinition to separate map
dmpolukhin a24e8db
Replace map with set
dmpolukhin b887050
Fix formatting
dmpolukhin 0a99d89
Add corresponding changes in MultiplexExternalSemaSource
dmpolukhin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| // RUN: %clang_cc1 -std=c++20 -verify -emit-llvm-only %s | ||
|
|
||
| template <int> | ||
| void Create(const void* = nullptr); | ||
|
|
||
| template <int> | ||
| struct ObjImpl { | ||
| template <int> | ||
| friend void ::Create(const void*); | ||
| }; | ||
|
|
||
| template <int I> | ||
| void Create(const void*) { | ||
| (void) ObjImpl<I>{}; | ||
| } | ||
|
|
||
| int main() { | ||
| Create<42>(); | ||
| } | ||
|
|
||
| // expected-no-diagnostics |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clang AST is open to modifications.
Can't you add a new bit to
Redeclarableto keep track of this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a problem with adding more flags to
FunctionDecl,FunctionDeclBitfieldsis full and I cannot add there anything.Redeclarabledoesn't have any flags as the moment and we need this extra flag only for FunctionDecls at the moment. So new version of the code works but most probably it cannot be committed as is. I also added another test case for the same example but inside module. My previous version was not able to compile it correctly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can do this in ASTReader (ExternalASTSource). We can add a new interface to ExternalASTSource and calling it. It will be helpful since the call to
wasThisDeclarationADefinition()should be cold.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ChuanqiXu9 sorry I'm not sure I fully understand your idea about ExternalASTSource. Are you suggesting to extend
ASTReader::DefinitionSourceto also keep this information there? NowASTReader::DefinitionSourcemaps toboolbut I can change value to a struct with two flags (previous DefinitionSource and ThisDeclarationWasADefinition), I think we don't need to store it in PCM file. Does it sound like the right approach?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes, I took the last free bit in FunctionDeclBits a couple of months ago :)
This is a tall order, but it may be possible to make room in there. For example:
It looks like
IsExplicitlyDefaultedonly makes sense ifIsDefaultedis true, and maybe your new stuff only makes sense ifIsDefaultedis false, so you canprobably share the
IsExplicitlyDefaultedbit.if that doesn't work, there are some other potential candidates.
For example, some bit fields only make sense if the function has a body, like
UsesSEHTry, and these bits would probably be free for you as well.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can add bits by shrinking
NumCtorInitializers.
however, in the present case it doesn't seem justified. these bits are precious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer ExternalASTSource approach because it won't add any additional memory overhead and we already have hashtable ASTReader::DefinitionSource. Access to the filed should be super cold so it won't slowdown things. I will update this PR soon.