-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[core] Fold AutoloadLibraryMU into AutoloadLibraryGenerator #16969
base: master
Are you sure you want to change the base?
Conversation
Test Results 18 files 18 suites 3d 19h 47m 57s ⏱️ Results for commit c0fd8cb. ♻️ This comment has been updated with latest results. |
Use AbsoluteSymbolsMaterializationUnit to define the symbols.
2c0bc2e
to
c0fd8cb
Compare
As far as I could understand, Lang recommends this simplification, so marking as ready for review |
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.
Do we have any performance numbers? Is the absolute symbol approach similar in terms of computational cost?
llvm::orc::SymbolMap loadedSymbols; | ||
for (const auto &KV : found) { | ||
// Try to load the library which should provide the symbol definition. | ||
// TODO: Should this interface with the DynamicLibraryManager directly? |
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.
Yes, ideally that'd be a good idea...
I'm not sure I understand, this PR is just moving the code from the MU to the Generator. |
I think it answers my question. |
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.
Lgtm!
Use
AbsoluteSymbolsMaterializationUnit
to define the symbols.