Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

NGEN: verify that we process handle indirections correctly #656

Closed
erozenfeld opened this issue Jun 18, 2015 · 0 comments · Fixed by #690
Closed

NGEN: verify that we process handle indirections correctly #656

erozenfeld opened this issue Jun 18, 2015 · 0 comments · Fixed by #690
Assignees
Milestone

Comments

@erozenfeld
Copy link
Member

Any differences in how handles should be interpreted (no indirection, single indirection, double indirection) is already abstracted via InfoAccessType enum. When we get a handle from the CLR we also get an InfoAccessType value:

// Can a value be accessed directly from JITed code.
enum InfoAccessType
{
IAT_VALUE, // The info value is directly available
IAT_PVALUE, // The value needs to be accessed via an indirection
IAT_PPVALUE // The value needs to be accessed via a double indirection
};

We need to make sure the existing code is correct for the new codepaths.

@erozenfeld erozenfeld self-assigned this Jun 18, 2015
@erozenfeld erozenfeld added this to the Sprint 85 milestone Jun 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant