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 60174a82 for ; Mon, 3 Feb 2020 16:20:07 +0000 (UTC) Received: (qmail 10221 invoked by uid 550); 3 Feb 2020 16:20:06 -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 10203 invoked from network); 3 Feb 2020 16:20:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=dHMdSsjZnAUNxN49DDs4qHWHIcCzbVj68LGYH4rtwz4=; b=SvE6dBilJOnmiAVqrq0/94lX0vEtcZrC0UItGL1trNbZNf++BXYbkfxQjBCyZAIVrA /vSjRYTitTQal8EhgaXBuoq3M8a3kDlN1Q3BSVJJIvfE7JmKf6NLRXvTzTQDLnA8q+RP UxSel2TuFKuPn0BZNX8GROcXPm8al+/FuBm7G07qUp1yAAplTOe1GE0X9yf3Lmh1le+W GXYihT1ta2PRL8ROcXxtrHEE8DYOLL6R8E2B16sbUtOcUt55d6wvaIBo9Pi7/rYUVEGl Y7Of2wF7ntUJeQPBhQ+4hCr0m2vWA6f+ZTCQB2vTBbQANRc6ARIhdTSuFBASIDiM6QeQ pazQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=dHMdSsjZnAUNxN49DDs4qHWHIcCzbVj68LGYH4rtwz4=; b=YVkReE2n6HQFq485zd65gzNWA7RCL5CyOmLe2bnKgcJoCG6BieaUNogGrPEbgvMHiD GHzPVHYghLMUyqN67VX0thV4aL1RmdwXYTiMn/ZvgqmhaeYYaGo0bW61zsw1PM8S/3QC LWrffwzJwRkNOPrDBYCtzTV9S5p6xrpl7kLRmeVWd63LQkHrSGZrk9rOAhKykW4UQYsN MuObBFEMLv31Bp6vFSYADhykh263EXm5Zjq/JKCbGUfs404zB77Vg3OsY4rehlsRJJT9 wpwyTIjbZqzBxOZtjsqYFevmUSRPnmOx7ql+L5sQ4hSInKGbMTDazS8isijpMqoDeRwI IYyg== X-Gm-Message-State: APjAAAVoCI4u95IdWuIoxUhjt7v/ZPWxhEJNAYAztctjTUkYvaa2zs1s tmE8rdF4IA4/6mS7Rv5IqkBSvnYmaVC72LG43ZhOCk3I X-Google-Smtp-Source: APXvYqz6/TIDkMFot2vlsia859FnKSO4RmzfWuvXROOjxEzkLiV8dic/uBBXx1gPgi+sCJ8UdW0+t4L/9A/YfjtjXiM= X-Received: by 2002:a05:600c:2944:: with SMTP id n4mr29563891wmd.22.1580746793857; Mon, 03 Feb 2020 08:19:53 -0800 (PST) MIME-Version: 1.0 References: <05c1e691-c0b6-f1af-4850-68670f2d915d@gmail.com> <20200203145030.GP1663@brightrain.aerifal.cx> In-Reply-To: From: David Edelsohn Date: Mon, 3 Feb 2020 11:18:42 -0500 Message-ID: To: musl@lists.openwall.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [musl] PPC64(LE) support in musl requires ALTIVEC On Mon, Feb 3, 2020 at 11:04 AM Jeffrey Walton wrote: > > On Mon, Feb 3, 2020 at 10:43 AM Romain Naour wro= te: > > > > Le 03/02/2020 =C3=A0 15:50, Rich Felker a =C3=A9crit : > > > 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/se= tjmp.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. > > I'm not sure if it matters or how it relates here, but I believe IBM > compilers (XL C and XL C++) do not allow Altivec until Power5. I think > the decision was more policies and procedures, though. Power5 was the > first ABI specification from the OpenPower group. > > Other compilers supported Altivec earlier then Power5. For example, > Apple's GCC supported Altivec at least as early as Power3. And I have > a PowerMac that is Power4 and Altivec works fine. The PPC64LE ELFv2 ABI specifies Power8 with VSX as the minimum ISA. Musl is free to ignore that. The rest of the discussion above about processor support for Altivec is wrong, but correcting that is off topic. Thanks, David