We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Symbol table initialization (populating InputFile::symbol[*]) is easier to parallelize than symbol resolution.
InputFile::symbol[*]
See https://reviews.llvm.org/D62188 https://reviews.llvm.org/D62290 from ELF.
Then, in the --start-lib (#52931) state, InputFile::symbols can be saved to be reused by non-lazy ObjFile::parse BitcodeFile::parse (see D116390).
--start-lib
InputFile::symbols
ObjFile::parse
BitcodeFile::parse
Future direction: introduce a mode to do eager parsing. The prerequisite is to replace ArchiveFile with lazy ObjFile/BitcodeFile.
ArchiveFile
ObjFile
BitcodeFile
The text was updated successfully, but these errors were encountered:
@llvm/issue-subscribers-lld-MachO
Sorry, something went wrong.
No branches or pull requests
Symbol table initialization (populating
InputFile::symbol[*]
) is easier to parallelize than symbol resolution.See https://reviews.llvm.org/D62188 https://reviews.llvm.org/D62290 from ELF.
Then, in the
--start-lib
(#52931) state,InputFile::symbols
can be saved to be reused by non-lazyObjFile::parse
BitcodeFile::parse
(see D116390).Future direction: introduce a mode to do eager parsing. The prerequisite is to replace
ArchiveFile
with lazyObjFile
/BitcodeFile
.The text was updated successfully, but these errors were encountered: