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

[x64[r2r] ObjectStackAllocationTests is broken after #21950 #11826

Closed
sandreenko opened this issue Jan 17, 2019 · 0 comments · Fixed by dotnet/coreclr#22088
Closed

[x64[r2r] ObjectStackAllocationTests is broken after #21950 #11826

sandreenko opened this issue Jan 17, 2019 · 0 comments · Fixed by dotnet/coreclr#22088

Comments

@sandreenko
Copy link
Contributor

The output shows:

FAILURE (AllocateSimpleClassAndCheckTypeNoHelper): unexpected allocation of 24 bytes

Started to fail afer dotnet/coreclr#21950.

CI example:.

PTAL @erozenfeld , cc @dotnet/jit-contrib

erozenfeld referenced this issue in erozenfeld/coreclr Jan 19, 2019
AllocateSimpleClassAndCheckTypeNoHelper fails because
the object is allocated on the heap in R2R mode. The reason for that is
that we always use a helper for isinst in R2R mode and helper calls
cause us to assume the object escapes.

We don't have to use a helper in this case (even for R2R), #22086 tracks
fixing that.

For now the fix is not to check that the object was allocated on the stack
in this test case.

Fixes #22026.
erozenfeld referenced this issue in dotnet/coreclr Jan 23, 2019
AllocateSimpleClassAndCheckTypeNoHelper fails because
the object is allocated on the heap in R2R mode. The reason for that is
that we always use a helper for isinst in R2R mode and helper calls
cause us to assume the object escapes.

We don't have to use a helper in this case (even for R2R), #22086 tracks
fixing that.

For now the fix is not to check that the object was allocated on the stack
in this test case.

Fixes #22026.
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants