diff options
| author | Alan Modra <amodra@gmail.com> | 2013-11-21 06:12:35 -0500 |
|---|---|---|
| committer | Anthony Green <green@moxielogic.com> | 2013-11-21 21:24:56 -0500 |
| commit | ab79d6e21992dd86139ba07530ff888833b78a04 (patch) | |
| tree | 3ed261655ba53cd2269dba583d6f3bf561adb34d /man | |
| parent | 69df91cfb4fa6bcb644350a80bff970f27478a6a (diff) | |
| download | libffi-ab79d6e21992dd86139ba07530ff888833b78a04.tar.gz | |
This separates the 32-bit sysv/linux/bsd code from the 64-bit linux
code, and makes it possible to link code compiled with different
options to those used to compile libffi. For example, a
-mlong-double-128 libffi can be used with -mlong-double-64 code.
Using the return value area as a place to pass parameters wasn't such
a good idea, causing a failure of cls_ulonglong.c. I didn't see this
when running the mainline gcc libffi testsuite because that version of
the test is inferior to the upstreamm libffi test.
Using NUM_FPR_ARG_REGISTERS rather than NUM_FPR_ARG_REGISTERS64 meant
that a parameter save area could be allocated before it was strictly
necessary. Wrong but harmless. Found when splitting apart ffi.c
into 32-bit and 64-bit support.
Diffstat (limited to 'man')
| -rw-r--r-- | man/Makefile.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/man/Makefile.in b/man/Makefile.in index 8e786d3..fb60d20 100644 --- a/man/Makefile.in +++ b/man/Makefile.in @@ -187,6 +187,7 @@ FFI_EXEC_TRAMPOLINE_TABLE = @FFI_EXEC_TRAMPOLINE_TABLE@ FGREP = @FGREP@ GREP = @GREP@ HAVE_LONG_DOUBLE = @HAVE_LONG_DOUBLE@ +HAVE_LONG_DOUBLE_VARIANT = @HAVE_LONG_DOUBLE_VARIANT@ INSTALL = @INSTALL@ INSTALL_DATA = @INSTALL_DATA@ INSTALL_PROGRAM = @INSTALL_PROGRAM@ |