From: Brian Sullivan <briansul@microsoft.com>
Date: Thu, 20 Apr 2017 22:53:19 +0000 (-0700)
Subject: When we have profile data we can have cross module references in our ZapSig's when... 
X-Git-Tag: accepted/tizen/base/20180629.140029~1321^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e13760cf8f64a4070ecbe4390a9d3b3170fe5de8;p=platform%2Fupstream%2Fcoreclr.git

When we have profile data we can have cross module references in our ZapSig's when building ReadyToRun images.
We should return a null TypeHandle to indicate failure so that we don't attempt to add generic types/methods
that have cross module references.  (i.e. MyList<System.Guid> )
---

diff --git a/src/vm/siginfo.cpp b/src/vm/siginfo.cpp
index b9955ec..82aef45 100644
--- a/src/vm/siginfo.cpp
+++ b/src/vm/siginfo.cpp
@@ -1199,7 +1199,10 @@ TypeHandle SigPointer::GetTypeHandleThrowing(
             
             PREFIX_ASSUME(pZapSigContext != NULL);
             pModule = pZapSigContext->GetZapSigModule()->GetModuleFromIndex(ix);
-            if (pModule != NULL)
+
+            // For ReadyToRunCompilation we return a null TypeHandle when we reference a non-local module
+            //
+            if ((pModule != NULL) && pModule->IsInCurrentVersionBubble())
             {
                 thRet = psig.GetTypeHandleThrowing(pModule, 
                                                    pTypeContext,