From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.2 Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by inbox.vuxu.org (OpenSMTPD) with SMTP id 2a89fc25 for ; Mon, 3 Feb 2020 15:43:06 +0000 (UTC) Received: (qmail 23766 invoked by uid 550); 3 Feb 2020 15:43:05 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 23748 invoked from network); 3 Feb 2020 15:43:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fY8CmRWBAa6qV4wjW6Ve3bxptmlgqXMHcOAwLn2G+54=; b=qBpJ3tDszRdi5C7M44si8BfVDo+7yYRMm/rvc6mmoWGAaifer5F+TlgIBlzW6SKR2G LZusK5JlW1igb0K5HNe3el4tIwhcVIKOhQ/dWeR8d81D1AFkHQxGr0G20T26gR436jZR kXzP6nWGv0laWE/sfHEfCH2oa5ChbCLOla5yeOothDn4HM5pRwk/OrRlslJqPKl+oUe3 duR5O1gUrgq+CSD35W+9PTLedoOaZPENcwA0cQ8OXPI+MnjR6cZZLPhMjeMepi23Z1M7 la7URLV0pW5FIOV0IlbOyoM2t5iPxSXnyWgDEGAto33R5GZpljrEtl48KdpsFd7TQ8Z6 QK4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fY8CmRWBAa6qV4wjW6Ve3bxptmlgqXMHcOAwLn2G+54=; b=Q3k2F5CZIzViQRYMWGenQtzWdOkjzkXWv0Y0EMv9K0Y2gUhK9LIaKw+vqsBJKxM3Yl QcupRtPHR6tFH3erBtGQBWcrKSAf8holTOmaoHH/nuSN/5fSqQ9sepc5xwx3i5Wn7ub9 4fSWhbzqysS5w3eCkJjcWnVAvxboPzLoGp4VmQh4Q5kqk0iWs6OATDT+SvknjPAJ6uKg /7BV9GHVRhttEc6f5AQD387Vp2nO2obacA+2HM9DVh55j/aZ8/nP9mqLWZtdoh+xeBZP Sqoe4jh9Gb8lYRy672VychrlROsCGnvn8nmMFKLJYhwljU3wWXlcLuPNIZ7UPJ9ENe/w pVsg== X-Gm-Message-State: APjAAAUTq3HFS98acRLeZGz+9MG8rPkkv4RGf/OeZoFZgkAEOtavi16D lx4BK8/JeTQY8fx3eXEKXFs= X-Google-Smtp-Source: APXvYqy/6u0kLBOwMKFKVuaflzPEsNxmf1FC1O3Jcp37zTmrP3UBcD+MYklscRldC0xW12uPYt0KEg== X-Received: by 2002:a05:6000:1284:: with SMTP id f4mr15583197wrx.379.1580744573160; Mon, 03 Feb 2020 07:42:53 -0800 (PST) To: musl@lists.openwall.com, Rich Felker References: <05c1e691-c0b6-f1af-4850-68670f2d915d@gmail.com> <20200203145030.GP1663@brightrain.aerifal.cx> From: Romain Naour Message-ID: Date: Mon, 3 Feb 2020 16:42:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20200203145030.GP1663@brightrain.aerifal.cx> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [musl] PPC64(LE) support in musl requires ALTIVEC Hi, Le 03/02/2020 à 15:50, Rich Felker a écrit : > On Mon, Feb 03, 2020 at 03:16:17PM +0100, Romain Naour wrote: >> Hi, >> >> We noticed that musl toolchain doesn't work on PPC64 e5500 cpus due to >> Altived instructions in src/setjmp/powerpc64/setjmp.s [1]. >> >> A patch has been sent by Vincent Fazio to the Buildroot mailing list to disable >> musl for such cpus [2]. >> >> Maybe the supported-platforms list could be updated [3]. >> >> [1] https://git.musl-libc.org/cgit/musl/tree/src/setjmp/powerpc64/setjmp.s#n74 >> [2] http://patchwork.ozlabs.org/patch/1231986/ >> [3] https://wiki.musl-libc.org/supported-platforms.html > > Is this like the 32-bit Freescale things with the weird alternate FPU? Indeed, it seems that the only one ppc64 cpu without Altivec support. > We support those for ppc32 as soft-float (and AIUI the ABI for use > with the FPU matches soft-float ABI, so in theory it could be > supported but we were never clear on whether it's IEEE-conforming) but > I wasn't aware of anything like that for 64-bit so it was never added. > Assuming it's the same concept, I don't see a reason we couldn't add > it. I'm not sure it worth the effort, I don't have a particular interest on this cpu. I'm fine if this case is not supported. The issue was discovered by toolchain-builder [1] project (a Buildroot side project for building cross toolchains) due to issue while testing the system with Qemu. If upcoming version of musl support this cpu, we will re-enable musl for it. [1] https://toolchains.bootlin.com Best regards, Romain > > Rich >