-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
PMI assert in system.private.corelib #11200
Comments
@AndyAyersMS dotnet/coreclr#19420 added new overload APIs for these intrinsic. The JIT implementations and test cases are in dotnet/coreclr#20210 |
Are you saying this is an expected failure until we've merged dotnet/coreclr#20210? If so: in the (not too distant) future we may be adding PMI runs to the CI, so we'll have to stage changes like this differently. |
Yes, it probably is expected (but I am not very familiar with PMI tests). In the current master,
Recently, we are changing some APIs of hardware intrinsic https://github.com/dotnet/coreclr/issues/20062. Once the work gets done, we won't have this kind of failures. |
@AndyAyersMS dotnet/coreclr#20210 is merged, could you please try again? |
Trying... it now. I am currently hitting an assert in crossgen now. Let me see if this repros with a clean build...
|
Looks like the above was a transient issue. And PMI is ow working on corelib again,. |
Thanks! |
PMI now asserts when processing system.private.corelib on x64 checked:
possibly from dotnet/coreclr#19420
cc @fiigii @dotnet/jit-contrib
The text was updated successfully, but these errors were encountered: