-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
CctorForWrite failing with NativeAOT #84400
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch, @kunalspathak Issue DetailsThis: runtime/src/tests/Loader/classloader/TypeInitialization/CctorsWithSideEffects/CctorForWrite.cs Lines 22 to 25 in e45e5db
Gets generated as:
Notice we grab the cctor base before the call, hitting exactly what the test is testing we shouldn't be doing. Not sure what effect #83911 is going to have on this, but it's failing right now. I'm surprised we're not seeing it in ReadyToRun testing because this is a ReadyToRun pattern. (We're not seeing this in NativeAOT testing because we're still in the process of standing up these tests in regular testing.) Cc @markples
|
R2R issue for this is #84007 |
Oh, I did see the test was introduced in a PR from January but I thought we would have dealt with a possible R2R issue in the 3 months since then. I didn't realize the January PR only merged last week. It's probably a dupe of the R2R issue. |
Closing it for the duplicate. |
This:
runtime/src/tests/Loader/classloader/TypeInitialization/CctorsWithSideEffects/CctorForWrite.cs
Lines 22 to 25 in e45e5db
Gets generated as:
Notice we grab the cctor base before the call, hitting exactly what the test is testing we shouldn't be doing.
Not sure what effect #83911 is going to have on this, but it's failing right now. I'm surprised we're not seeing it in ReadyToRun testing because this is a ReadyToRun pattern. (We're not seeing this in NativeAOT testing because we're still in the process of standing up these tests in regular testing.)
Cc @markples
The text was updated successfully, but these errors were encountered: