Bitcode upgrade automatically takes in place when the current compiler version doesn't match the one building the input modules. The upgrade is very expansive for large applications and unnecessary when users are sure the two compilers do not have a version issue, even if their versions mismatch literally. An optional to disable the automatic bitcode upgrade will be handy in such case.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Object/IRSymtab.cpp | ||
---|---|---|
436 | Upgrade for this case is probably always needed to recreate symbol table. I think that bypassing upgrade from benign version mismatch is all we need. Correspondingly, we could rename the switch as diisable-bitcode-version-upgrade. WDYT? |
llvm/lib/Object/IRSymtab.cpp | ||
---|---|---|
436 | Good point. Symbol table mismatch isn't what we are targeting. |
Upgrade for this case is probably always needed to recreate symbol table. I think that bypassing upgrade from benign version mismatch is all we need. Correspondingly, we could rename the switch as diisable-bitcode-version-upgrade. WDYT?