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

Make ObjectStackAllocationTests work correctly under crossgen2 #40096

Merged
merged 1 commit into from
Jul 29, 2020

Conversation

davidwrighton
Copy link
Member

  • Add a mechanism for passing arbitrary arguments to the crossgen2 process while running crossgen2 tests
  • Pass the --codegenopt JitObjectStackAllocation=1 when compiling this test with Crossgen2. This will result in enabling the object stack allocation feature during compilation
  • As Crossgen2 currently disregards the debuggable attribute when deciding codegen mode, detect the presence running crossgen2 and expect allocation to occur on the stack even if S.P.C is debuggable

Fixes #32729

@davidwrighton
Copy link
Member Author

@dotnet/crossgen-contrib

Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for fixing! I guess that at some point I should publish the RunCrossGen2 and CompositeBuildMode in the r2rtest ProcessRunner too to make test behavior consistent in the presence of such runtime checks.

@davidwrighton davidwrighton merged commit a4bd2fb into dotnet:master Jul 29, 2020
Jacksondr5 pushed a commit to Jacksondr5/runtime that referenced this pull request Aug 10, 2020
…ossgen2 (dotnet#40096)

- Add a mechanism for passing arbitrary arguments to the crossgen2 process while running crossgen2 tests
- Pass the `--codegenopt JitObjectStackAllocation=1` when compiling this test with Crossgen2. This will result in enabling the object stack allocation feature during compilation
- As Crossgen2 currently disregards the debuggable attribute when deciding codegen mode, detect the presence running crossgen2 and expect allocation to occur on the stack even if S.P.C is debuggable
@karelz karelz added this to the 5.0.0 milestone Aug 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
@davidwrighton davidwrighton deleted the CG2ObjectStackAllocation branch April 20, 2021 17:43
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.

Test failure in JIT/opt/ObjectStackAllocation/ObjectStackAllocationTests/ObjectStackAllocationTests.sh
4 participants