[PATCH] D43199: [IRMover] Implement name based structure type mapping

Rafael Avila de Espindola via llvm-commits llvm-commits at lists.llvm.org
Wed Feb 14 08:20:21 PST 2018


Evgeny Leviant <eleviant at accesssoftek.com> writes:

>> This suggests that ThinLTO should be changed. It is fine to start with a
>> non empty module, but it should scan its types so that Foo is found to
>> be isomorphic to Bar an not imported.
>
> I don't see how this can be done as you can have both Foo and Bar imported from different modules and still get mapping failure.
> The problem is that addNonOpaque registers a single entry for all isomorphic structure types. Can you please elaborate your idea?

I am not sure I follow. If they are imported from different modules we
are in the same situation as llvm-link, no? Importing two modules into a
third one.

Cheers,
Rafael


More information about the llvm-commits mailing list