tree 6da5a9a6c7adce6bf6e0a119fd432fd29ac6bcb8
parent 65d5267aacca46d408ddc090563714e50f3a910e
author Julius Werner <jwerner@chromium.org> 1563937213 -0700
committer Julius Werner <jwerner@chromium.org> 1563938734 -0700

Use explicit-width data types in AAPCS parameter structs

It's not a good idea to use u_register_t for the members of
aapcs64_params_t and aapcs32_params_t, since the width of that type
always depends on the current execution environment. This would cause
problems if e.g. we used this structure to set up the entry point of an
AArch32 program from within an AArch64 program. (It doesn't seem like
any code is doing that today, but it's probably still a good idea to
write this defensively. Also, it helps with my next patch.)

Change-Id: I12c04a85611f2b6702589f3362bea3e6a7c9f776
Signed-off-by: Julius Werner <jwerner@chromium.org>