From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66995 invoked by alias); 27 Nov 2019 09:28:05 -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 66986 invoked by uid 89); 27 Nov 2019 09:28:05 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 spammy=U*doko, download X-HELO: mail-lf1-f45.google.com Received: from mail-lf1-f45.google.com (HELO mail-lf1-f45.google.com) (209.85.167.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Nov 2019 09:28:03 +0000 Received: by mail-lf1-f45.google.com with SMTP id y5so3851082lfy.7 for ; Wed, 27 Nov 2019 01:28:03 -0800 (PST) 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:content-transfer-encoding; bh=cCzUk0J5HbIRNomvSduQnx9PSDJbvppOiwWUp8oyWR4=; b=Z2obJo472qv+j+66IG78UGUwwGL/EKuBdHrL4ElzckT/6wUb2+Bv0WUjbGxdb7cj8b ZVfLJb99Z/P4QjYETzX7hwM160n1QNIdmdDnIPcB+d5r+o9/PDFEXD+FLelIMYCHR9h3 0IkCHuU/9XIq+S2asaQQwwpflUKs5B/bVqAJWUS3L7WogiAeiSMQAYw+ZsNmNY2HeD1y Q9Th1vwzlwjce4O3stmhyMAHDqjL0a4sQaT8D8wuw9k8Vk019ipW501Ivdj0GZHzds0l rqnCeYFLRl7sipb++cSxxNkPNxzi+Q7c1g0rDaDYO9a7fd8JFFC/a6S8/jJRV3O+YOEf 9z6w== MIME-Version: 1.0 References: <816931f1-7ff7-60bf-82c1-e2221b1ec1dd@ubuntu.com> In-Reply-To: <816931f1-7ff7-60bf-82c1-e2221b1ec1dd@ubuntu.com> From: Anthony Green Date: Wed, 27 Nov 2019 09:28:00 -0000 Message-ID: Subject: Re: libffi 3.3 release candidate 1 To: Matthias Klose Cc: libffi-discuss Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00093.txt.bz2 Yes, can you try changing the __int128 to "alignas(16) char[16]" ? https://github.com/libffi/libffi/pull/526 https://github.com/libffi/libffi/issues/531 AG On Wed, Nov 27, 2019 at 2:54 AM Matthias Klose wrote: > > On 24.10.19 13:16, Anthony Green wrote: > > libffi 3.3 release candidate 1 is available for testing... > > > > https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-= rc1.tar.gz > > https://github.com/libffi/libffi/releases/tag/v3.3-rc1 > > the libffi-3.3.tar.gz published last Friday now ftbfs on powerpc-linux-gn= u: > > libtool: compile: powerpc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I. > -I../include -Iinclude -I../src -Wdate-time -D_FORTIFY_SOURCE=3D2 -g -O2 > -fdebug-prefix-map=3D/<>=3D. -fstack-protector-strong -Wform= at > -Werror=3Dformat-security -Wall -fexceptions -MT src/powerpc/ffi.lo -MD -= MP -MF > src/powerpc/.deps/ffi.Tpo -c ../src/powerpc/ffi.c -fPIC -DPIC -o > src/powerpc/.libs/ffi.o > In file included from ../src/powerpc/ffi.c:33: > ../src/powerpc/ffi_powerpc.h:65:9: error: =E2=80=98__int128=E2=80=99 is n= ot supported on this target > 65 | typedef __int128 float128; > | ^~~~~~~~ > make[3]: *** [Makefile:1274: src/powerpc/ffi.lo] Error 1 > make[3]: Leaving directory '/<>/build' > make[2]: *** [Makefile:1348: all-recursive] Error 1