Minor README fix.
This commit is contained in:
@@ -3,7 +3,7 @@ libffi-ios provides an experimental port of libffi to Apple's iOS.
|
|||||||
The libffi closure mechanism has previously required the use of executable data pages, however, iOS sandbox restrictions prevent their use.
|
The libffi closure mechanism has previously required the use of executable data pages, however, iOS sandbox restrictions prevent their use.
|
||||||
The OS does, however, permit remapping of executable pages, allowing one to remap a single page to multiple locations. libffi-ios modifies
|
The OS does, however, permit remapping of executable pages, allowing one to remap a single page to multiple locations. libffi-ios modifies
|
||||||
ffi_closure_alloc/ffi_closure_free APIs to make use of this functionality to implement dynamically allocated and configured closure
|
ffi_closure_alloc/ffi_closure_free APIs to make use of this functionality to implement dynamically allocated and configured closure
|
||||||
trampoline's without requiring the use of executable data.
|
trampolines without requiring the use of executable data.
|
||||||
|
|
||||||
The implementation works by allocating a writable config page, and then remapping a page of pre-compiled trampolines directly
|
The implementation works by allocating a writable config page, and then remapping a page of pre-compiled trampolines directly
|
||||||
after the config page. The trampolines use PC-relative addressing to load their context from the config page, and so it is possible
|
after the config page. The trampolines use PC-relative addressing to load their context from the config page, and so it is possible
|
||||||
|
|||||||
Reference in New Issue
Block a user