Allow building for mipsel with Android NDK r8. From Mozilla bug 756740.
https://bugzilla.mozilla.org/show_bug.cgi?id=756740
Ensure the linker supports @unwind sections in libffi. From Mozilla bug 756740.
https://bugzilla.mozilla.org/show_bug.cgi?id=778414

Also tracked as issue #42.
https://github.com/atgreen/libffi/issues/42
Replace double quotes with single quotes in Makefile.in to improve compatibility between some versions of MSYS and gmake. From Mozilla bug 943728.
https://bugzilla.mozilla.org/show_bug.cgi?id=943728
Remove stray hunk that shouldn't have been included in this patch.
Merge pull request #81 from rvandermeulen/bug-756740

Allow building for mipsel with Android NDK r8.
Fix merge
Ensure the linker supports @unwind sections in libffi.
Remove autogenerated files from the repository

Add an autogen.sh to regenerate them.
Merge pull request #87 from joshtriplett/autogen

Remove autogenerated files from the repository
Re-add libtool-ldflags
Merge pull request #92 from joshtriplett/autogen

Re-add libtool-ldflags
testsuite/libffi.call/many.c: Avoid spurious failure due to excess precision

The test case testsuite/libffi.call/many.c can spuriously fail due to
excess floating-point precision.  Instrumenting it with some printf
calls shows differences well above FLT_EPSILON.  (Note when
instrumenting it that multiple computations of the difference, such as
one in a print and another in the conditional, may produce different
results.)

Rather than complicating the test suite with architecture-specific flags
to avoid excess precision, just simplify the floating-point computation
to avoid a dependency on potential excess precision.
testsuite/libffi.call/many_win32.c: Avoid spurious failure due to excess precision

The test case testsuite/libffi.call/many_win32.c can spuriously fail due
to excess floating-point precision.  Instrumenting it with some printf
calls shows differences well above FLT_EPSILON.  (Note when
instrumenting it that multiple computations of the difference, such as
one in a print and another in the conditional, may produce different
results.)

Rather than complicating the test suite with architecture-specific flags
to avoid excess precision, just simplify the floating-point computation
to avoid a dependency on potential excess precision.
ChangeLog: Document many.c and many_win32.c changes to avoid spurious failures
Merge pull request #88 from joshtriplett/such-precision-many-fail-wow

testsuite/libffi.call/many.c: Avoid spurious failure due to excess precision
testsuite: Remove fragile stack pointer checks

testsuite/libffi.call/closure_stdcall.c and
testsuite/libffi.call/closure_thiscall.c include inline assembly to save
the stack pointer before and after the call, and compare the values.
However, compilers can and do leave the stack in different states for
these two pieces of inline assembly, such as by saving a temporary value
on the stack across the call; observed with gcc -Os, and verified as
spurious through careful inspection of disassembly.
Merge pull request #91 from joshtriplett/esp-extra-stackery-perception

testsuite: Remove fragile stack pointer checks
ChangeLog: Document testsuite changes to remove fragile stack pointer checks
Merge pull request #94 from joshtriplett/esp-extra-stackery-perception

ChangeLog: Document testsuite changes to remove fragile stack pointer checks
.travis.yml: Test on both 32-bit and 64-bit