-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Jit preparation for arm64 apple: Use bytes in
fgArgTabEntry
. (#42503)
* fix a dumping error introduced in my recent ref PR. * add a pinvoke test with many small stack arguments. It will fail on arm64 apple. * Add get/set for lclVar::lvStkOffs. * Change some types from `size_t` to `unsigned` when working with stack offsets. * Rename `stackSize` to `GetStackSize`. * Do not run stack level setter for arm64 apple. * Use bytes in `fgArgTabEntry`. * fix comments/rename vars. * Add en explanation about `GetStackSlotsNumber`. * Rename `DEBUG_NOT_OSX_ARM64` to `DEBUG_ARG_SLOTS`.
- Loading branch information
Sergey Andreenko
authored
Oct 1, 2020
1 parent
eb91a96
commit 334bd84
Showing
19 changed files
with
525 additions
and
268 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.