-
Notifications
You must be signed in to change notification settings - Fork 5k
JIT: Move passed-by-reference argument information to new ABI info #112449
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
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
PTAL @dotnet/jit-contrib @dotnet/samsung @shushanhf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
#if FEATURE_IMPLICIT_BYREFS | ||
dsc->lvIsImplicitByRef = lvaParameterPassingInfo[i].IsPassedByReference(); | ||
#endif // FEATURE_IMPLICIT_BYREFS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have found in the past Marking V%02i as a byref parameter
from below to be a useful crumb to have a quick understanding of which parameters are by-ref. Preserve it by moving here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It currently gets printed by ABIPassingInformation::Dump
, so at the top of the JIT dump you will see:
static void Foo(long a, object b, Guid c, List<string>.Enumerator d)
{
}
Parameter V00 ABI info: [00..08) reg x0
Parameter V01 ABI info: [00..08) reg x1
Parameter V02 ABI info: 2 segments
[0] [00..08) reg x2
[1] [08..16) reg x3
Parameter V03 ABI info: [00..08) reg x4 (implicit by-ref)
Let me know what you think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
No description provided.