libffi

samsonium/libffi

Fork 0

mirror of https://github.com/partic2/libffi synced 2026-11-11 02:27:19 +00:00

Commit Graph

Author	SHA1	Message	Date
Saleem Abdulrasool	79d1509cb0	x86: align alloca to 16-byte boundary Align the stack allocation to a 16-byte boundary. This ensures that the stack parameters are 16-byte aligned which is needed for some instructions.	2017-10-22 14:09:51 -07:00
Saleem Abdulrasool	7ad0ae7f42	arm: zext return value parameters The closure function (invoked as closure->fun in ffi_closure_XXX_inner) will only populate the actual number of bytes for the true return type, which may be a character. This leaves garbage on the stack when the assembly closure function (i.e. ffi_closure_XXX) reads the return value off of the stack into r0 as a 4-byte value. ffi_closure_XXX always leaves room for at least 4 bytes here, so we can safely set them to 0. Otherwise, if there is garbage in any of these bytes, these end up in r0 and in the returned value as well.	2017-10-10 11:46:20 -07:00

Author

SHA1

Message

Date

Saleem Abdulrasool

79d1509cb0

x86: align alloca to 16-byte boundary

Align the stack allocation to a 16-byte boundary.  This ensures that the
stack parameters are 16-byte aligned which is needed for some
instructions.

2017-10-22 14:09:51 -07:00

Saleem Abdulrasool

7ad0ae7f42

arm: zext return value parameters

The closure function (invoked as closure->fun in ffi_closure_XXX_inner)
will only populate the actual number of bytes for the true return type,
which may be a character.  This leaves garbage on the stack when the
assembly closure function (i.e. ffi_closure_XXX) reads the return value
off of the stack into r0 as a 4-byte value.  ffi_closure_XXX always
leaves room for at least 4 bytes here, so we can safely set them to 0.
Otherwise, if there is garbage in any of these bytes, these end up in r0
and in the returned value as well.

2017-10-10 11:46:20 -07:00