[PATCH] D30738: Don't internalize llvm GV's with InternalizeLinkedSymbols

Teresa Johnson via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Thu Mar 9 16:08:12 PST 2017


tejohnson added a comment.

In https://reviews.llvm.org/D30738#697051, @pcc wrote:

> The fix can be simplified to
>
>   if (P.first().startswith("llvm."))
>     continue;
>
>
> That is two lines of code. Even if we simplified the internalize pass in the same way, we should not add this much complexity just to avoid duplicating two lines.


Sure that is simple from a # lines standpoint, but the internalizer already had all the right logic, so we wouldn't have had this issue if we used internalizeModule to start with. My original suggestion was to move it out of here completely and have the clients invoke internalizeModule directly if they want to internalize, since I'm not sure the module linker should be in the business of doing internalization.


Repository:
  rL LLVM

https://reviews.llvm.org/D30738





More information about the llvm-commits mailing list