提交 ce8043b0 编写于 作者: J Jan Vorlicek 提交者: Jan Kotas

Fix overlooked moduleIndex initial value (dotnet/coreclr#24881)

When adding the signature copying some time ago, I have overlooked one
place where the moduleIndex was set to -1 instead of MODULE_INDEX_NONE.
I was using the -1 during the development and replaced it by creating
MODULE_INDEX_NONE during final cleanup at all but one places.

This caused issues during crossgen even without large version bubble
enabled. Methods requiring generic constraint were not crossgen-ed due
to this.

Commit migrated from https://github.com/dotnet/coreclr/commit/795f2fd2a67047519b477cd1776626368c88e73c
上级 d646dffb
......@@ -1530,7 +1530,7 @@ BOOL ZapSig::EncodeMethod(
{
_ASSERTE(pConstrainedResolvedToken->cbTypeSpec > 0);
DWORD moduleIndex = (DWORD)-1;
DWORD moduleIndex = MODULE_INDEX_NONE;
if (IsReadyToRunCompilation() && pMethod->GetModule()->IsInCurrentVersionBubble() && pInfoModule != (Module *) pConstrainedResolvedToken->tokenScope)
{
moduleIndex = (*((EncodeModuleCallback)pfnEncodeModule))(pEncodeModuleContext, (Module *) pConstrainedResolvedToken->tokenScope);
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册