JIT: Skip tailcall IR validation for struct calls #96719
Conversation
When structs are involved the correct return patterns can be very complex if they involve decomposed field stores produced by physical promotion. Skip the validation for these cases.
ghost
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsWhen structs are involved the correct return patterns can be very complex if they involve decomposed field stores produced by physical promotion. Skip the validation for these cases.
|
|
/azp run runtime-coreclr libraries-jitstress |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
cc @dotnet/jit-contrib PTAL @AndyAyersMS Ideally we would be able to move all identification of tailcalls to one place and make it IR based (e.g. based on this checker) but unfortunately the existence of explicit tailcalls makes that hard since it means we always need to have an invariant that explicit tailcalls are properly performed. Given that the completeness of this checker is less interesting to maintain. |
When structs are involved the correct return patterns can be very complex if they involve decomposed field stores produced by physical promotion. Skip the validation for these cases.
2 participants
When structs are involved the correct return patterns can be very complex if they involve decomposed field stores produced by physical promotion. Skip the validation for these cases.
Fix #96715