Skip to content

Remove LocAllocSP for non-x86 platforms #11269

@BruceForstall

Description

@BruceForstall

In functions with localloc, we allocate a stack variable to store the RSP after the most recent localloc. This is named the LocAllocSP variable in the JIT. But it doesn’t look like it’s ever read; it’s only written. And it isn’t reported in the GC info.

So why do we do it? Is it a holdover from some older JIT32 implementation?

The one subtlety to investigate is whether the VM uses this in some way. Note that in some cases, especially for x86, we don't explicitly report all variable stack locations -- we report one, and then expect others to exist and be in a particular relative order.

Metadata

Metadata

Assignees

Labels

area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions