-
Bug
-
Resolution: Fixed
-
P4
-
repo-panama
-
aarch64
-
os_x
Consider a C function like this:
void f(int, int, int, int, int, int, int, int, char x, short y);
In the standard AArch64 ABI x and y get spilled to the stack as eight byte quantities (as if they were assigned to a register and then spilled) but in the Mac ABI they are spilled to the stack with their original size and natural alignment. AArch64 CallArranger needs to handle this difference.
void f(int, int, int, int, int, int, int, int, char x, short y);
In the standard AArch64 ABI x and y get spilled to the stack as eight byte quantities (as if they were assigned to a register and then spilled) but in the Mac ABI they are spilled to the stack with their original size and natural alignment. AArch64 CallArranger needs to handle this difference.
- is blocked by
-
JDK-8283462 VMReg should encode stack locations as byte offsets instead of slots
- Open
- relates to
-
JDK-8284041 Explicitly reject unsupported call shapes on macos-aarch64
- Resolved