-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Delete gtNewBlkOpNode and lvSimdBaseJitType
#85848
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
Delete gtNewBlkOpNode and lvSimdBaseJitType
#85848
Conversation
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsBoth not needed anymore.
|
src/coreclr/jit/importer.cpp
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
volatile. is not allowed for cpobj per the specification, and we would BADCODE in impValidateMemoryAccessOpcode if we did encounter it.
ab6d821 to
54f531e
Compare
Note: neither "initobj" nor "cpobj" can be preceded by "volatile.". Delete the self-assignment handling Block morphing will fold it to a NOP anyway. I do not see the referenced liveness bug still being present. It seems to have been a remnant of COPYBLK/COPYOBJ days. Move the SIMD logic to gtNewAssignNode Delete "gtNewBlkOpNode"
4f37363 to
589aa2c
Compare
|
Diffs - one case on x86 where a SIMD local is no longer promoted. @dotnet/jit-contrib |
Both not needed anymore.