Vlad Tsyrklevich 444617b4b3 IRMover: Account for matching types present across modules
Summary:
Due to uniqueing of DICompositeTypes, it's possible for a type from one
module to be loaded into another earlier module without being renamed.
Then when the defining module is being IRMoved, the type can be used as
a Mapping destination before being loaded, such that when it's requested
using TypeMapTy::get() it will fail with an assertion that the type is a
source type when it's actually a type in both the source and
destination modules. Correctly handle that case by allowing a non-opaque
non-literal struct type be present in both modules.

Fix for PR37684.

Reviewers: pcc, tejohnson

Reviewed By: pcc, tejohnson

Subscribers: tobiasvk, mehdi_amini, steven_wu, llvm-commits, kcc

Differential Revision: https://reviews.llvm.org/D47898

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@335145 91177308-0d34-0410-b5e6-96231b3b80d8
2018-06-20 16:50:56 +00:00
..
2017-08-15 20:29:24 +00:00
2016-07-04 08:01:29 +00:00
2016-04-08 18:15:37 +00:00