JIT: clean up unescaped only stored-to objects

Open
#116,163 4 comments 3 reactions 1 assignee View on GitHub

@AndyAyersMS is already working on this.

Since Jun 16, 2025.

Assessment

This issue has not been assessed yet.

Description

area-CodeGen-coreclr

We see these in particular after stack allocation. We might be able to clean them up early in the SSA phases.

See comment stream starting here: https://github.com/dotnet/runtime/issues/84872#issuecomment-2920947328

We also might be able to avoid some of this by recognizing dead allocations in escape analysis, though that might be trickier.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.