kc3-lang/libffi/src
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
e5f0eb15 | 2019-10-08 06:58:52 | Clean up line endings (#509) The CLRF visual studio files can be kept that way, but recognized as text. The assembly file can be converted to LF. | |
 |
ea9b6639 | 2019-10-08 05:57:28 | PowerPC bugfixes (#520) * powerpc: Silence warnings about unused labels * powerpc: Fix a couple of comments * powerpc: Fix alignment after float structs * powerpc: Don't pad rvalues copied from FP regs * powerpc: Add missing check in struct alignment * powerpc: Support homogeneous long double structs | |
 |
c2a68590 | 2019-08-07 11:57:45 | fix mingw build and crashing bugs for Python Windows ARM64 (#496) * fix mingw build and crashing bugs for Python Windows ARM64 * Fix issues found in PR review | |
 |
d856743e | 2019-06-26 07:31:22 | libffi: added ARM64 support for Windows (#486) * libffi: added ARM64 support for Windows 1. ported sysv.S to win64_armasm.S for armasm64 assembler 2. added msvc_build folder for visual studio solution 3. updated README.md for the same 4. MSVC solution created with the changes, and below test suites are tested with test script written in python. libffi.bhaible libffi.call 5. Basic functionality of above test suites are getting passed Signed-off-by: ossdev07 <ossdev@puresoftware.com> * Update README.md | |
 |
fadf1eb5 | 2019-04-27 20:53:29 | hppa: avoid TEXTREL in .eh_frame section (#447) Before the change hand-crafted .eh_frame section contained ABS relocation and caused TEXTREL tag to be emitted: ``` $ ./configure --host=hppa2.0-unknown-linux-gnu LDFLAGS=-Wl,-z,text $ make ... /usr/libexec/gcc/hppa2.0-unknown-linux-gnu/ld: read-only segment has dynamic relocations. ``` Link failure is caused by absolute address of FDEs encoded into .eh_frame entries. Fixed TEXTREL by using pcrel (instead of ABS) encoding for absolute addresses (__PIC__ code) by adding augmentation information ("zR" CIE type). All tests still pass on hppa2.0. The specific tests that still pass and exercise this code path: testsuite/libffi.call/unwindtest.cc testsuite/libffi.call/unwindtest_ffi_call.cc Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> | |
 |
06bf1a9d | 2019-04-28 03:21:44 | fix x86/x64 MSVC build (#487) | |
|
db5706ff | 2019-04-26 04:58:58 | add support for 32-bit ARM on Windows (#477) * add support for 32-bit ARM on Windows * fix mismatched brace in appveyor.yml * remove arm platform from appveyor.yml for now * fix arm build * fix typo * fix assembler names * try Visual Studio 2017 * add windows arm32 to .appveyor.yml * update README.md | |
 |
a7d6396f | 2019-03-29 14:19:20 | fix check for Linux/aarch64 fixes #473 | |
 |
05a17964 | 2019-02-19 04:11:28 | Cleanup symbol exports on darwin and add architecture preprocessor checks to assist in building fat binaries (eg: i386+x86_64 on macOS or arm+aarch64 on iOS) (#450) * x86: Ensure _efi64 suffixed symbols are not exported * x86: Ensure we do not export ffi_prep_cif_machdep Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * x86: Ensure we don't export ffi_call_win64, ffi_closure_win64, or ffi_go_closure_win64 Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * closures: Silence a semantic warning libffi/src/closures.c:175:23: This function declaration is not a prototype Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * aarch64: Ensure we don't export ffi_prep_cif_machdep Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * arm: Ensure we don't export ffi_prep_cif_machdep Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * aarch64, arm, x86: Add architecture preprocessor checks to support easier fat builds (eg: iOS) Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * x86: Silence some static analysis warnings libffi/src/x86/ffi64.c:286:21: The left operand of '!=' is a garbage value due to array index out of bounds libffi/src/x86/ffi64.c:297:22: The left operand of '!=' is a garbage value due to array index out of bounds Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * aarch: Use FFI_HIDDEN rather than .hidden Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> * ffi.h: Don't advertise ffi_java_rvalue_to_raw, ffi_prep_java_raw_closure, and ffi_prep_java_raw_closure_loc when FFI_NATIVE_RAW_API is 0 Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> | |
|
e1118af5 | 2019-02-19 03:58:25 | changes for win32 on windows (#468) | |
 |
44a6c285 | 2019-02-19 12:55:11 | aarch64: Flush code mapping in addition to data mapping (#471) This needs a new function, ffi_data_to_code_pointer, to translate from data pointers to code pointers. Fixes issue #470. | |
 |
4a84df4a | 2018-10-31 15:53:54 | Fix Q registers parameter passing on ARM64 The second two quads are located at offset 32 not 16 | |
 |
a5ea7527 | 2018-09-19 07:29:36 | Merge pull request #443 from jeremyhu/master Update FFI_HIDDEN() to use .private_extern on Apple platforms and use the macro where appropriate | |
 |
e6eac786 | 2018-09-18 15:19:53 | Prefix ALIGN_DOWN macro with FFI_ | |
 |
4cb776bc | 2018-08-09 12:12:29 | RISC-V go closures This implements go closures for RISC-V. It has been tested on riscv64-suse-linux and against the libgo testsuite. | |
 |
ba73a671 | 2018-07-20 09:37:43 | Update FFI_HIDDEN() to use .private_extern on Apple platforms and use the macro where appropriate Fix issue #439 Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> | |
|
65da63ab | 2018-06-25 04:38:58 | Add compact unwind for darwin/i386 (#440) * x86: Add implementation of compact unwind for ffi_call_i386, et al. Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> * x86: Use __text as the section name to avoid deprecated section name warnings. Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> * darwin: Add missing regular,debug attributes for compact unwind sections Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> | |
 |
2309b584 | 2018-06-17 17:04:24 | Mark sysv.S as SafeSEH compatible (#438) It contains no exception handler, so we can just emit the special @feat.00 symbol to indicate that it's trivially SafeSEH compatible. SafeSEH only applies to x86 and not x86-64, hence its inclusion in the x86-specific block. See [1] for details. [1] https://msdn.microsoft.com/en-us/library/windows/desktop/ms680547(v=vs.85).aspx#the_.sxdata_section_ | |
|
1d704051 | 2018-06-17 17:01:50 | i386: Fix missing break; in case statement leading to incorrectly returned FFI_BAD_ABI (#437) * i386: Add missing break triggering dead store static analyzer checks. Register calling sequence is being reported as bad ABI instead of working as intended. Found-by: Clang Static Analysis Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> * Mark ffi arm sysv entry points as private_extern. Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> * x86_64: Add implementation of compact unwind for ffi_call_unix64. Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@apple.com> | |
 |
b55baf0b | 2018-05-09 13:21:02 | Handle FFI_GNUW64 on non-Windows systems (EFI) | |
|
b5ee3957 | 2018-05-05 07:41:53 | Revert "Remove some symbol exports and cleanup newline warnings (#433)" This reverts commit a5a0f3cf36dfb4d64316414a872288c3170e6c1d. | |
|
a5a0f3cf | 2018-05-05 03:44:33 | Remove some symbol exports and cleanup newline warnings (#433) * build: Ensure darwin generated sources end with a new line Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> * build: Use .private_extern where missing to prevent exporting symbols that are not API Signed-off-by: Jeremy Huddleston Sequoia <jeremyhu@macports.org> | |
 |
d3c54cf3 | 2018-05-02 06:19:58 | Re-enable msabi testing (#436) * Revert "disable msabi testing for now" This reverts commit 7b7638eb0eac2adfa72f7ec9f254ba287c9947e2. * x86: Correct testing for 64-bit x86-64 Since passing -m32 to x86-64 compiler will generate i386 code, we need to check both __ILP32__ and __i386__ for 64-bit x86-64. * x86: Check __i386__ instead of i?86-*-* targets Since passing -m32 to x86-64 compiler will generate i386 code, we need to check __i386__ instead of i?86-*-* targets for i386 targets. * i386: Properly passing integer parameters in registers For thiscall and fastcall, if the paramter passed as 64-bit integer or struct, all following integer paramters will be passed on stack. * test: Add ABI_ATTR to callback_code Add ABI_ATTR to callback_code to properly test different ABIs. | |
 |
ebf24166 | 2018-05-02 13:55:29 | PowerPC64 ELFv1 fp arg fixes The ELFv1 ABI says: "Single precision floating point values are mapped to the second word in a single doubleword" and also "Floating point registers f1 through f13 are used consecutively to pass up to 13 floating point values, one member aggregates passed by value containing a floating point value, and to pass complex floating point values". libffi wasn't expecting float args in the second word, and wasn't passing one member aggregates in fp registers. This patch fixes those problems, making use of the existing ELFv2 homogeneous aggregate support since a one element fp struct is a special case of an homogeneous aggregate. I've also set a flag when returning pointers that might be used one day. This is just a tidy since the ppc64 assembly support code currently doesn't test FLAG_RETURNS_64BITS for integer types.. * src/powerpc/ffi_linux64.c (discover_homogeneous_aggregate): Compile for ELFv1 too, handling single element aggregates. (ffi_prep_cif_linux64_core): Call discover_homogeneous_aggregate for ELFv1. Set FLAG_RETURNS_64BITS for FFI_TYPE_POINTER return. (ffi_prep_args64): Call discover_homogeneous_aggregate for ELFv1, and handle single element structs containing float or double as if the element wasn't wrapped in a struct. Store floats in second word of doubleword slot when big-endian. (ffi_closure_helper_LINUX64): Similarly. | |
|
4c2206ac | 2018-04-28 04:46:10 | Fix two "return" issues in x86/ffi64.c (#431) Issue #70 pointed out that at least one compiler didn't like: return ffi_call_efi64(cif, fn, rvalue, avalue); ... where the return type is "void". This patch splits the statement into two. I also noticed that ffi_call_go here seems to do a double call. I suspect a "return" is missing here, so this patch adds it as well. | |
 |
7d3cab79 | 2018-04-21 00:24:50 | xtensa-linux: use cache flush instruction only if it is available (#426) | |
 |
159b94e5 | 2018-04-19 01:28:23 | Various MIPS Fixes (#425) * mips: simplify closure #defines This commit should have no visible effect. * mips: add special handling of variadic functions MIPS requires special handling of variadic functions which pass floating point arguments: * In the o32 ABI, all float arguments are passed in integer registers. * In the n32/n64 ABIs, float arguments after the ellipsis are passed in integer registers. Implement this in libffi. To support this in n32/n64 closures, we need to add a new mips_nfixedargs field to ffi_cif which will break the libffi ABI. This fixes the libffi.call/cls_longdouble_va.c test which was failing on 64-bit MIPS. * mips: align argn for all 64-bit types in o32 closure handler Ensure that argn is pre-aligned for all 64-bit argument types (including doubles) and not just integer types. This fixes closures of the form "f(float, double, <some integer args>)". Previously the first integer argument would be read from a2 which is garbage at this point (the float arguments have already "consumed" a0-a3). After this commit, argn is correctly padded between the "float" and "double" arguments so that the first integer argument is read from the stack. Fixes "double f(float,double,int)" test in #371 * mips: do not read from floating point register if returning a struct In the o32 ABI, the pointer passed in a0 used to return structures indirectly is treated as the first argument for argument allocation purposes. This means that it should inhibit floating point registers the same way that other integer arguments do. Fixes "Double f(float,Double,double)" test in #371 * mips: fix pointer cast warnings Fix two pointer cast warnings when compiled on 64-bit mips by casting through uintptr_t. Fixes mips64el part of #404 | |
|
e27f70b8 | 2018-04-08 18:25:34 | Fix case where callback arg value is split across regs and stack | |
 |
af6773d6 | 2018-04-02 13:55:31 | Fix appveyor windows build (#420) * Fix msvcc dll build by adding dllexport decorations to all API declarations * Fix appveyor build for VS 2013 Use the new -DFFI_BUILDING_DLL for producing a working DLL. Update the msvcc.sh wrapper script to successfully compile the testsuite files. * MSVC build: suppress warnings in testsuite * fix testsuite on appveyor | |
|
369ef49f | 2018-03-18 12:53:42 | Add missing FFI_GNUW64 enum | |
|
43980dd1 | 2018-03-18 12:32:10 | Add FFI_GNUW64 ABI for GNU 80-bit long double support | |
|
9bc40d87 | 2018-03-18 12:32:10 | Add FFI_GWIN64 ABI for GNU 80-bit long double support | |
 |
d4640608 | 2018-03-18 07:00:42 | Fully allocate file backing writable maps (#389) When ftruncate() is used on a filesystem supporting sparse files, space in the file is not actually allocated. Then, when the file is mmap'd and libffi writes to the mapping, SIGBUS is thrown to the calling application. Instead, always fully allocate the file that will back writable maps. | |
|
6a801d04 | 2018-03-16 17:53:33 | Fix closure case where 8-byte value is partially passed in register. Fixes cls_many_mixed_float_double test case. | |
|
01db31d9 | 2018-03-13 20:41:55 | Update moxie sub opcode | |
 |
3840d49a | 2018-03-11 05:55:15 | New RISC-V port (#281) * Add RISC-V support This patch adds support for the RISC-V architecture (https://riscv.org). This patch has been tested using QEMU user-mode emulation and GCC 7.2.0 in the following configurations: * -march=rv32imac -mabi=ilp32 * -march=rv32g -mabi=ilp32d * -march=rv64imac -mabi=lp64 * -march=rv64g -mabi=lp64d The ABI currently can be found at https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md . * Add RISC-V to README * RISC-V: fix configure.host | |
|
dca52b55 | 2018-03-11 08:50:01 | Merge pull request #406 from trofi/master ia64: fix variadic function closures with FP arguments | |
|
83d9aba3 | 2018-03-11 08:48:42 | Merge pull request #407 from trofi/ia64-small-struct ia64: fix small struct return | |
|
e66fd678 | 2018-02-20 10:47:09 | Revert "Fix passing struct by value on aarch64" This reverts commit 482b37f00467325e3389bab322525099860dd9aa. That was actually a bug in python, see <https://bugs.python.org/issue30353>. | |
|
b58caef7 | 2018-02-17 19:00:40 | ia64: fix small struct return This change fixes libffi.call/struct10.c failure on ia64: FAIL: libffi.call/struct10.c -W -Wall -Wno-psabi -O0 execution test .Lst_small_struct handles returns for structs less than 32 bytes (following ia64 return value ABI [1]). Subroutine does roughly the following: ``` mov [sp+0] = r8 mov [sp+8] = r9 mov [sp+16] = r10 mov [sp+24] = r11 memcpy(destination, source=sp, 12); ``` The problem: ia64 ABI guarantees that top 16 bytes of stack are scratch space for callee function. Thus it can clobber it. [1] says (7.1 Procedure Frames): """ * Scratch area. This 16-byte region is provided as scratch storage for procedures that are called by the current procedure. Leaf procedures do not need to allocate this region. A procedure may use the 16 bytes at the top of its own frame as scratch memory, but the contents of this area are not preserved by a procedure call. """ In our case 16 top bytes are clobbered by a PLT resolver when memcpy() is called for the first time. As a result memcpy implementation reads already clobbered data frop top of stack. The fix is simple: allocate 16 bytes of scrats space prior to memcpy() call. [1]: https://www.intel.com/content/dam/www/public/us/en/documents/guides/itanium-software-runtime-architecture-guide.pdf Bug: https://bugs.gentoo.org/634190 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> | |
|
11de69dd | 2018-02-11 11:29:39 | ia64: fix variadic function closures with FP arguments libffi test framework already flagged failures as: ``` FAIL: libffi.call/cls_double_va.c -W -Wall -Wno-psabi -O0 output pattern test, is 7.0 res: 4 0.0 res: 4 ? should match 7.0 ?es: 4 ?.0 res: 4 ``` Failure happens here at ```c // testsuite/libffi.call/cls_double_va.c ... char* format = "%.1f\n"; double doubleArg = 7; ... CHECK(ffi_prep_closure_loc(pcl, &cif, cls_double_va_fn, NULL, code) == FFI_OK); res = ((int(*)(char*, ...))(code))(format, doubleArg); ``` libffi expects 'doubleArg' to be located in 'f9' (second FP argument) but gcc placed it to 'r33' (second GR). ia64 software [1] manual described argument passing ABI in "8.5.2 Register Parameters" as: """ If an actual parameter is known to correspond to a floating-point formal parameter, the following rules apply: a) The actual parameter is passed in the next available floating-point parameter register, if one is available. Floating-point parameter registers are allocated as needed from the range f8-f15, starting with f8. b) If all available floating-point parameter registers have been used, the actual parameter is passed in the appropriate general register(s). (This case can occur only as a result of homogeneous floating-point aggregates, described below.) If a floating-point actual parameter is known to correspond to a variable-argument specification in the formal parameter list, the following rule applies: c) The actual parameter is passed in the appropriate general register(s). If the compiler cannot determine, at the point of call, whether the corresponding formal parameter is a varargs parameter, it must generate code that satisfies both of the above conditions. (The compiler’s determination may be based on prototype declarations, language standard assumptions, analysis, or other user options or information.) """ We have [c] case here and gcc uses only GR for parameter passing. The change binds known variadic arguments ro GRs instead of FPs as those are always expected to be initialized for all variadic call types. This fixes all 10 failures on ia64-unknown-linux-gnu: ``` === libffi Summary === -# of expected passes 1945 -# of unexpected failures 10 + +# of expected passes 1955 ``` [1]: https://www.intel.com/content/dam/www/public/us/en/documents/guides/itanium-software-runtime-architecture-guide.pdf Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> | |
|
9429968b | 2018-02-10 23:23:33 | Merge pull request #403 from frida/fix/x86-sysv-pic-closure-regression Fix x86 SysV closure in PIC mode | |
|
482b37f0 | 2017-09-18 12:44:08 | Fix passing struct by value on aarch64 This fixes the ctypes test in the python testsuite. | |
 |
28d3b61b | 2018-01-20 23:56:17 | Fix x86 SysV closure in PIC mode The assembly single-line comments swallowed up the remaining assembly code of the macros due to lack of line-endings. This is a regression introduced in b7f6d7a. | |
|
bec6135d | 2018-01-10 07:20:04 | Merge pull request #393 from thejunkjon/master Linker error "recompile with -fPIC" for x86_64 | |
 |
746dbe3a | 2018-01-03 10:07:41 | mips/ffi.c: fix encoding for jr on r6 mips/ffi.c: instruction jr has a different encoding for r6 | |
|
94c102aa | 2017-12-10 14:25:01 | Not set mips on mips r6 MIPS release changed encodes of some instructions, include ll/sc etc. if .set mips4 on mips r6, as will generate some wrong encode of some instructions. | |
 |
d15581c6 | 2017-12-01 00:34:30 | Updating calls to ffi_closure_unix64_inner and ffi_closure_win64_inner to use PLT. Without this fix, statically linking libffi causes the linker error i.e. 'requires dynamic R_X86_64_PC32 reloc against ffi_closure_unix64_inner which may overflow at runtime; recompile with -fPIC)' | |
|
4fdbb057 | 2017-11-03 07:05:31 | Merge pull request #320 from 0-wiz-0/master Support NetBSD with mprotect. | |
|
b302bc3d | 2017-11-03 07:03:55 | Merge pull request #322 from compnerd/aarch64-base aarch64: fix index base register for AArch64 | |
 |
9fc9dc53 | 2017-10-27 16:12:56 | Fix linux detection (closes #303) | |
 |
1fb788ac | 2017-10-10 11:37:00 | aarch64: fix index base register for AArch64 The base is passed in `x3`, not in `x2`. This fixes the indexing base so that the right value is used. | |
|
dc2ff5ba | 2017-10-25 13:11:40 | Merge pull request #323 from compnerd/x86-alloca-alignment x86: align alloca to 16-byte boundary | |
|
927da716 | 2017-10-25 13:05:53 | Merge pull request #379 from jlj/master Xcode build improvements | |
|
a0455c03 | 2017-10-25 13:04:23 | Merge pull request #383 from hjl-tools/hjl/master Hjl/master | |
|
9d9d92b4 | 2017-10-25 04:59:31 | Skip WIN64/EFI64 support for x32 Since x32 doesn't support WIN64/EFI64, skip it if __ILP32__ is defined. | |
|
3c372c38 | 2017-10-24 13:53:56 | arm: fix a level of indirection issue Rather than relying on the stack being 0'ed out always, do it manually. The stack generally happened to be zero, and because the compiler realizes that the tests are dealing with chars truncates the read value. However, the top 3 nibbles of the value are undefined and may be non-zero. The indirection level caused a null-pointer dereference. Explicitly scribbling on the stack during the allocation causes test failures without the original zexting behaviour. | |
 |
181fc4cc | 2017-10-23 15:02:29 | Merge branch 'master' based on ksjogo/libffi Added a tvOS target in Xcode project. Misc Xcode project cleanup. Fix macOS build target in Xcode project. # Conflicts: # src/aarch64/ffi.c # src/x86/ffi64.c | |
|
79d1509c | 2017-10-10 11:39:45 | 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. | |
|
ed7488c0 | 2017-10-17 13:00:51 | src/ia64/unix.S: unbreak small struct handling commit 6e8a4460833594d5af1b4539178025da0077df19 added FFI_TYPE_COMPLEX value type (comes after FFI_TYPE_POINTER) ia64 ffi_closure_unix reiles on the ordering of FFI_ enums as ia64 has ia64-specific FFI types: small struct and FPU extesions. As a result all tests handling small structs broke. The change fixes dispatch table by adding (no-op) FFI_TYPE_COMPLEX entry This has positive effect of unbreaking most tests on ia64: === libffi Summary === -# of expected passes 1595 -# of unexpected failures 295 +# of expected passes 1930 +# of unexpected failures 10 # of unsupported tests 30 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> | |
|
7ad0ae7f | 2017-10-10 11:44:05 | 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. | |
 |
2bfcd299 | 2017-10-02 15:34:03 | Support NetBSD with mprotect. Signed-off-by: Thomas Klausner <wiz@NetBSD.org> | |
|
93d8e7dd | 2017-09-27 21:51:34 | Fix #265 | |
|
02a5145a | 2017-09-27 21:43:03 | Merge pull request #263 from ksjogo/master fix ios builds | |
|
10099d6c | 2017-09-27 20:54:09 | Merge pull request #271 from frida/fix/qnx-cache-flushing arm: Fix cache flushing on QNX | |
|
db4dad97 | 2017-09-27 20:47:08 | Merge pull request #312 from fjricci/fix_ub Fix misaligned memory access in ffi_call_int | |
|
a78da739 | 2017-09-04 15:55:34 | Fix macOS build target in Xcode project. - Add missing files for desktop platforms in generate-darwin-source-and-headers.py, and in the Xcode project. - Add a static library target for macOS. - Fix "implicit conversion loses integer precision" warnings for iOS mad macOS targets. | |
 |
9c12209d | 2017-08-03 10:46:28 | Fix misaligned memory access in ffi_call_int | |
 |
0ff9419f | 2017-05-17 14:57:53 | This patch enables FFI Go Closure on AIX. | |
|
bd72848c | 2017-04-27 13:20:36 | Prefix ALIGN macros with FFI_ | |
|
57d8ff04 | 2017-03-15 01:43:11 | Simplify iOS trampoline table allocation By using VM_FLAGS_OVERWRITE there is no need for speculatively allocating on a page we just deallocated. This approach eliminates the race-condition and gets rid of the retry logic. | |
 |
00406945 | 2016-07-12 16:08:42 | Update Xcodeproj Include all currently relevent files. Call autogen is build script. Fix compiler settings. Fix mach include. | |
|
a94c999b | 2017-03-19 07:36:07 | Handle fastcall declaration differently for some Microsoft compilers | |
|
a0b14eea | 2017-03-17 09:20:40 | Merge pull request #291 from ramon-garcia/visual-studio-build Build with Visual C++ (64 bits) | |
|
5e4fcdcc | 2017-03-15 01:43:11 | Simplify iOS trampoline table allocation By using VM_FLAGS_OVERWRITE there is no need for speculatively allocating on a page we just deallocated. This approach eliminates the race-condition and gets rid of the retry logic. | |
|
d42ce7b9 | 2017-03-15 01:23:40 | Fix error path so mutex is unlocked before returning In the unusual case where ffi_trampoline_table_alloc() fails. | |
 |
1e0d107b | 2017-01-08 20:12:59 | Modify configure.host to detect compilation with Microsoft Visual C++ and use assembly with Intel syntax in that case | |
 |
256ce51c | 2016-09-01 13:54:51 | Merge pull request #273 from wbx-github/master m68k: support ISA-A Coldfire CPUs | |
|
2ded2a4f | 2016-09-01 13:30:45 | Merge pull request #272 from yousong/mips64-soft-float Mips64 soft float | |
 |
b545ff81 | 2016-08-23 20:23:37 | ARC: Remove unused variable Signed-off-by: Yuriy Kolerov <yuriy.kolerov@synopsys.com> | |
 |
52a11f6d | 2016-08-20 00:52:19 | m68k: support ISA-A Coldfire CPUs Fix compilation for m68k/coldfire CPUs like mcf5208. Signed-off-by: Thorsten Glaser <tg@mirbsd.de> Signed-off-by: Waldemar Brodkorb <wbx@uclibc-ng.org> | |
 |
7a0d2c83 | 2016-08-15 15:00:13 | mips: fix MIPS softfloat build issue The patch for o32.S is taken from OpenWrt packages repo 3a7a4bf "libffi: fix MIPS softfloat build issue with current binutils" Signed-off-by: Felix Fietkau <nbd@openwrt.org> Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> | |
|
06d7c519 | 2016-08-10 15:06:16 | Merge pull request #269 from frida/fix/aarch64-variadic-closures-on-ios aarch64: Fix handling of variadic closures on iOS | |
|
aa7ed78c | 2016-08-10 15:03:37 | Merge pull request #268 from frida/fix/aarch64-large-aggregates aarch64: Fix handling of aggregates larger than 16 bytes | |
|
4da814b1 | 2016-08-10 22:48:09 | aarch64: Fix handling of aggregates larger than 16 bytes Instead of allocating stack space for a pointer we would allocate stack space for the actual aggregate size. | |
 |
ed848834 | 2016-08-10 14:57:22 | arm: Fix cache flushing on QNX Use `msync()` directly as `__clear_cache()` is broken in the qnx650_gcc4.8.3 toolchain. | |
|
5e9ac7e2 | 2016-08-10 15:22:19 | aarch64: Fix warning about unused function on iOS | |
|
4d1f11f6 | 2016-08-10 15:21:42 | aarch64: Fix operand size warning reported by Clang | |
|
301166b1 | 2016-08-10 15:59:56 | aarch64: Fix handling of variadic closures on iOS | |
|
cf4b2a50 | 2016-06-17 10:09:44 | Don't dereference "ecif" before NULL check Fixes #260 | |
|
794a54d4 | 2016-06-05 14:57:00 | Mark win64.S with GNU-stack note | |
 |
52fbd12d | 2016-05-26 09:00:00 | [Darwin-ppc, build] Fixes for clang build. clang is experimental on powerpc-darwin, but the changes are appropriate to cctools as as well. Use the 'official' simplified cmpwi insn, rather than the implied one accepted by cctools. Do not re-use a set value. | |
|
92810b4b | 2016-05-26 08:56:51 | [Darwin-x86, build] Fix up label prefixes, remove .purgem Darwin uses a label prefix of _. cctools assembler will not accept .purgem as a directive. | |
 |
74b3f520 | 2016-05-19 18:05:36 | Remove unused FFI_CLOSURE_TEST It was here since the first commit c6dddbd (warning: huge diff) and it wasn't defined by the configure script. It was probably used manually during development. | |
|
0969a1c1 | 2016-05-18 10:09:28 | Merge pull request #232 from berkerpeksag/signcompare Fix -Wsign-compare warnings in x86/ffi64.c | |
|
1e82e1cd | 2016-03-07 18:38:10 | Define _GNU_SOURCE on Linux for mremap() This was committed to CPython's libffi copy in https://bugs.python.org/issue10309 mremap() documentation says _GNU_SOURCE needs to be defined in order to use mremap(): see the synopsis section at http://linux.die.net/man/2/mremap Original commit: https://hg.python.org/cpython/rev/9986fff720a2 Original patch was written by Hallvard B Furuseth. | |
|
4a677a42 | 2016-03-05 09:58:38 | Fix -Wsign-compare warnings in x86/ffi64.c This was originally reported on the Python tracker: httpa://bugs.python.org/issue23958 The original patch was written by Steve R. Hastings. I've updated it to current master of libffi. | |
|
9443eaed | 2016-05-17 17:04:50 | Merge pull request #242 from somasis/master Fix usage on musl libc | |
|
48bfae1f | 2016-05-02 20:58:57 | Merge pull request #236 from andreas-schwab/master Define FFI_SIZEOF_JAVA_RAW for aarch64 ILP32 | |
 |
e169ba2b | 2016-04-29 21:04:07 | Fix usage on musl libc A gcc compiled on musl does not define __gnu_linux__, it defines __linux__. Only on glibc does __gnu_linux__ get defined, but both define __linux__, so we should check for that instead. With this patch, libffi works perfectly, and passes its testsuite entirely on musl libc systems. |