[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libffi 3.3 release candidate 1

On Fri, Oct 25, 2019 at 6:08 AM Matthias Klose <doko@ubuntu.com> wrote:
test results from

Thank you, Matthias!

i386 (i686-linux-gnu), hurd-i386, kfreebsd-i386:

Running ../../testsuite/libffi.bhaible/bhaible.exp ...
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=53
-Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
-Wno-uninitialized -O2 -DABI_NUM=FFI_STDCALL -DABI_ATTR=__STDCALL__ execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=53
-Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable
-Wno-uninitialized -O2 -fomit-frame-pointer -DABI_NUM=FFI_STDCALL
-DABI_ATTR=__STDCALL__ execution test

There's a pending stdcall patch.  I wanted to research more, as I seem to recall something about Microsoft/GCC incompatibility on this front.

As for m68k, or sh4 -- let me check the test cases carefully, but I don't plan on fixing either of those platforms myself.

There's a known problem with the riscv port, in that it doesn't promote results to the natural word size - but we don't have a test case for this in the suite.

So my plan is to add a test case for this, possibly commit the stdcall patch, and make release candidate 2.


Reply to: