Depends on D27076
Details
Diff Detail
- Build Status
Buildable 1757 Build 1757: arc lint + arc unit
Event Timeline
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
79 | Why don't you take all the members here? |
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
141 | Can you turn SymTab and File to be reference? | |
146–147 | Non relevant for this patch, but it'd be nice to document getName vs getIRName, I always forget when I look at this. | |
220–221 | Looks like something to add to ModuleSymbolTable. |
- Address review comments
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
79 | We need to create the module using the LLVMContext owned by this class. I suppose that given that we need to do that we might as well be consistent with the other members and let MBRef be default initialized as well. | |
141 | Done for SymTab. File may be null (see addRegularLTO) so I've left it as a pointer. | |
146–147 | It looks like getIRName is only used by the implementation, so I've removed it in r288302 and added documentation for getName. | |
220–221 | Maybe not, given our discussion on D27073. |
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
84 | It seems there is not much that still requires us to keep Mod here, what is fundamentally the remaining issue? |
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
84 | The major ones are:
Essentially we need it to access information that will later be stored in the bitcode symbol table. But until that's ready there's no harm in accessing the module directly. |
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
84 | Owning the module is only useful for the two other parts right? Technically we could store the source file name directly and extract the "used" early. |
llvm/include/llvm/LTO/LTO.h | ||
---|---|---|
84 | An owner is also needed for the GlobalValues stored in ModuleSymbolTable. But that's just another example of something that can be refactored with the bitcode symbol table. |
Why don't you take all the members here?
It seems strange to see the initialization and then File->Mod = ...