From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111823 invoked by alias); 21 Oct 2017 18:31:51 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 110388 invoked by uid 89); 21 Oct 2017 18:31:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=HTo:U*libffi-discuss, H*Ad:U*libffi-discuss, legend X-HELO: mo4-p00-ob.smtp.rzone.de Received: from mo4-p00-ob.smtp.rzone.de (HELO mo4-p00-ob.smtp.rzone.de) (81.169.146.160) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 21 Oct 2017 18:31:46 +0000 X-RZG-AUTH: :Ln4Re0+Ic/6oZXR1YgKryK8brlshOcZlIWs+iCP5vnk6shH+AHjwLuWOHqf0zZRW X-RZG-CLASS-ID: mo00 Received: from bruno.haible.de (dslb-088-068-032-102.088.068.pools.vodafone-ip.de [88.68.32.102]) by smtp.strato.de (RZmta 42.8 DYNA|AUTH) with ESMTPSA id I0b719t9LIVhKeB (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Sat, 21 Oct 2017 20:31:43 +0200 (CEST) From: Bruno Haible To: libffi-discuss@sourceware.org Subject: test results on many platforms Date: Sat, 21 Oct 2017 18:31:00 -0000 Message-ID: <2437301.0N14NqkuRT@omega> User-Agent: KMail/5.1.3 (Linux/4.4.0-96-generic; KDE/5.18.0; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2017/txt/msg00020.txt.bz2 Hi, I tested libffi-3.2.1 (building from source, and then test it using the test suite from https://haible.de/bruno/gnu/libffi-testsuite.tar.gz ). I've registered individual bugs in https://github.com/libffi/libffi/issues . Here's a summary of the results: aix-powerpc-32-gcc FTBFS aix-powerpc-32-xlc FTBFS aix-powerpc-64-gcc FTBFS aix-powerpc-64-xlc FTBFS cygwin-32 failed-call, failed-callback cygwin-64 failed-call, failed-callback freebsd-arm64 OK freebsd-x86-32 test-call crash, failed-callback freebsd-x86-64 OK hpux-hppa-32 FTBFS hpux-hppa-64 FTBFS hpux-ia64-32 FTBFS hpux-ia64-64 FTBFS hurd-x86 OK irix-mips-32 FTBFS irix-mips-n32-cc FTBFS irix-mips-n32-gcc FTBFS kfreebsd-x86-64 OK linux-alpha test-call unaligned access linux-alpine-x86-64 test-callback crash linux-arm64 OK linux-armel failed-callback linux-armelhf FTBFS; failed-callback linux-centos6-x86-64 OK linux-centos7-x86-64 OK linux-hppa test-call crash linux-ia64 failed-call, failed-callback linux-m68k failed-call, failed-callback linux-mipseb-32 failed-call, failed-callback linux-mipseb-64 failed-call, failed-callback linux-mipseb-n32 failed-call, failed-callback linux-mipsel-32 failed-callback linux-mipsel-64 failed-callback linux-mipsel-n32 failed-callback linux-powerpc-32 failed-call, failed-callback linux-powerpc-64 failed-call, failed-callback linux-powerpc-64el failed-callback linux-s390-32 failed-call, failed-callback linux-s390-64 failed-call, failed-callback linux-sparc-32 test-call crash, failed-callback linux-sparc-64 test-call crash, failed-callback linux-x86-32 OK linux-x86-64 OK linux-x86-x32 FTBFS macosx-powerpc failed-call, failed-callback macosx-x86-32 FTBFS macosx-x86-64 test-callback crash macosx-x86-64-clang OK netbsd-sparc-32 test-call crash, test-callback crash netbsd-x86-32 OK netbsd-x86-64 test-callback crash openbsd-x86-32 test-call crash, failed-callback openbsd-x86-64 test-call crash solaris10-sparc-32-cc failed-call, failed-callback solaris10-sparc-32-gcc test-call crash, failed-callback solaris10-sparc-64-cc FTBFS solaris10-sparc-64-gcc test-call crash, failed-callback solaris10-x86-32-cc FTBFS solaris10-x86-32-gcc OK solaris10-x86-64-cc FTBFS solaris10-x86-64-gcc test-callback crash windows-mingw-32 failed-call, test-callback crash windows-mingw-64 test-call crash, failed-callback windows-msvc-32 FTBFS windows-msvc-64 FTBFS Legend: - FTBFS means "fails to build from source". - "test-call crash" means that the test program that exercises ffi_call() crashes. - failed-call means that ffi_call behaves badly at runtime, but no crash. - "test-callback crash" means that the test program that exercises ffi_closure crashes. - failed-callback means that ffi_closure behaves badly at runtime, but no crash. Best regards, Bruno