ARM64: Change the fixed return buffer argument to be handled as a non-standard argument #5940
Conversation
…standard argument We already have support for the handling of non-standard arguments and it is simpler and better to handle the fixed return buffer argument as a non-standard argument.
|
@dotnet-bot test Windows_NT arm64 Checked |
|
@dotnet-bot test Windows_NT arm64 Checked pri1r2r |
briansull
changed the title
…t is modified by fgMorphTree
|
@dotnet-bot test Windows_NT arm64 Checked |
|
@dotnet-bot test Windows_NT arm64 Checked pri1r2r |
briansull
changed the title
|
@BruceForstall PTAL |
|
LGTM |
|
Random comment |
|
@briansull What actually most likely happened here is that since the triggers have been modified a bunch, when you commented the random comment, it went back and checked previous comments for arm64 phrases. It found one and launched. |
|
Actually I noticed that the two Arm32 jobs (which are new) were running after Kylee1 commented. |
ARM64: Change the fixed return buffer argument to be handled as a non-standard argument Commit migrated from dotnet/coreclr@4fb8970
We already have support for the handling of non-standard arguments and
it is simpler and better to handle the fixed return buffer argument as a non-standard argument.