From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 87264 invoked by alias); 26 Oct 2019 11:35:25 -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 87251 invoked by uid 89); 26 Oct 2019 11:35:24 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 spammy=matthias, Matthias, H*c:alternative, UD:php X-HELO: mail-lj1-f173.google.com Received: from mail-lj1-f173.google.com (HELO mail-lj1-f173.google.com) (209.85.208.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 26 Oct 2019 11:35:22 +0000 Received: by mail-lj1-f173.google.com with SMTP id c4so6087878lja.11 for ; Sat, 26 Oct 2019 04:35:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=moxielogic-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+VRrm24kah/avwSG3Ke8TdmTpIX9u2uuznfg9+VYKlI=; b=WFXwEZubPBddyP5hLoi4wRZBl8T3bp7hJWoulEczneoQh/lu1zyo16QrEqOmBKnWDh KCq68feFqorx3AA8ydbZHMPq5ajP6/sMNUtV9BFbHgki2YTw6JXm14xInAAc0hEhfKct wxRNqEOAQg1yhZbCDZ44cXM9z/OcRQeagtIueF5EXAB7Iw02FfffHnczWnYfEMgN3iUN THCmK08uerAF32xjk5ruHRa7HDALzqeMGREZ6bVB49tJWX2JgBduy9V7d3Av6NeS6qTd peRUJ0t3zY+U0hovC5joreTkNoS6nwossML35hJxFFPwwd8WyyyQg/EuDYOsnNorz2pM ebyw== MIME-Version: 1.0 References: <34f2c328-d879-71f9-2c60-34045d452f38@ubuntu.com> In-Reply-To: <34f2c328-d879-71f9-2c60-34045d452f38@ubuntu.com> From: Anthony Green Date: Sat, 26 Oct 2019 11:35:00 -0000 Message-ID: Subject: Re: libffi 3.3 release candidate 1 To: Matthias Klose Cc: libffi-discuss , Debian m68k , debian-superh@lists.debian.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00049.txt.bz2 On Fri, Oct 25, 2019 at 6:08 AM Matthias Klose wrote: > test results from > https://buildd.debian.org/status/package.php?p=libffi&suite=experimental 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. AG >