Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Put the Crossgen2 assertion check in sync with actual intrinsic count #44624

Merged
merged 2 commits into from
Nov 13, 2020

Conversation

trylek
Copy link
Member

@trylek trylek commented Nov 13, 2020

Recent removal of two intrinsics from the CorInfoIntrinsics enumeration
started tripping the assertion failure verifying the expected number
of intrinsics. I'm just updating the expected count.

Thanks

Tomas

/cc @dotnet/crossgen-contrib

Recent removal of two intrinsics from the CorInfoIntrinsics enumeration
started tripping the assertion failure verifying the expected number
of intrinsics. I'm just updating the expected count.

Thanks

Tomas
Copy link
Member

@janvorli janvorli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

trylek added a commit to trylek/runtime that referenced this pull request Nov 13, 2020
@trylek
Copy link
Member Author

trylek commented Nov 13, 2020

Currently lab testing in combination with the CG2 SPC change: #44625

@@ -112,7 +112,7 @@ static IntrinsicHashtable InitializeIntrinsicHashtable()
table.Add(CorInfoIntrinsics.CORINFO_INTRINSIC_GetRawHandle, "AllocatorOf", "System", "Activator");

// If this assert fails, make sure to add the new intrinsics to the table above and update the expected count below.
Debug.Assert((int)CorInfoIntrinsics.CORINFO_INTRINSIC_Count == 34, "Please update intrinsic hash table");
Debug.Assert((int)CorInfoIntrinsics.CORINFO_INTRINSIC_Count == 32, "Please update intrinsic hash table");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would better to just delete this assert. It made sense when this was a separate project in CoreRT. It is not the case anymore.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, removed in 2nd commit.

@jkotas jkotas merged commit 6c1ae0d into dotnet:master Nov 13, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 13, 2020
@trylek trylek deleted the Crossgen2IntrinsicCount branch January 10, 2022 19:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants