From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28943 invoked from network); 2 Jun 2020 15:56:54 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 2 Jun 2020 15:56:54 -0000 Received: (qmail 7538 invoked by uid 550); 2 Jun 2020 15:56:52 -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 7505 invoked from network); 2 Jun 2020 15:56:51 -0000 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Date: Tue, 2 Jun 2020 17:56:37 +0200 From: Michal =?iso-8859-1?Q?Such=E1nek?= To: Daniel Kolesa Cc: Joseph Myers , libc-alpha@sourceware.org, eery@paperfox.es, musl@lists.openwall.com, Will Springer , Palmer Dabbelt via binutils , via libc-dev , linuxppc-dev@lists.ozlabs.org Message-ID: <20200602155637.GW25173@kitsune.suse.cz> References: <2047231.C4sosBPzcN@sheen> <20200602142337.GS25173@kitsune.suse.cz> <3aeb6dfe-ae23-42f9-ac23-16be6b54a850@www.fastmail.com> <20200602152724.GU25173@kitsune.suse.cz> <454e0d68-d69e-43fc-9a8c-0461dd5817a9@www.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <454e0d68-d69e-43fc-9a8c-0461dd5817a9@www.fastmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Subject: [musl] Re: ppc64le and 32-bit LE userland compatibility On Tue, Jun 02, 2020 at 05:40:39PM +0200, Daniel Kolesa wrote: > > > On Tue, Jun 2, 2020, at 17:27, Michal Suchánek wrote: > > On Tue, Jun 02, 2020 at 05:13:25PM +0200, Daniel Kolesa wrote: > > > On Tue, Jun 2, 2020, at 16:23, Michal Suchánek wrote: > > > > On Tue, Jun 02, 2020 at 01:40:23PM +0000, Joseph Myers wrote: > > > > > On Tue, 2 Jun 2020, Daniel Kolesa wrote: > > > > > > > > > > > not be limited to being just userspace under ppc64le, but should be > > > > > > runnable on a native kernel as well, which should not be limited to any > > > > > > particular baseline other than just PowerPC. > > > > > > > > > > This is a fairly unusual approach to bringing up a new ABI. Since new > > > > > ABIs are more likely to be used on new systems rather than switching ABI > > > > > on an existing installation, and since it can take quite some time for all > > > > > the software support for a new ABI to become widely available in > > > > > distributions, people developing new ABIs are likely to think about what > > > > > new systems are going to be relevant in a few years' time when working out > > > > > the minimum hardware requirements for the new ABI. (The POWER8 minimum > > > > > for powerpc64le fits in with that, for example.) > > > > That means that you cannot run ppc64le on FSL embedded CPUs (which lack > > > > the vector instructions in LE mode). Which may be fine with you but > > > > other people may want to support these. Can't really say if that's good > > > > idea or not but I don't foresee them going away in a few years, either. > > > > > > well, ppc64le already cannot be run on those, as far as I know (I don't think it's possible to build ppc64le userland without VSX in any configuration) > > > > What hardware are you targetting then? I did not notice anything > > specific mentioned in the thread. > > > > Naturally on POWER the first cpu that has LE support is POWER8 so you > > can count on all other POWER8 features to be present. With other > > architecture variants the situation is different. > > This is not true; nearly every 32-bit PowerPC CPU has LE support (all the way back to 6xx), these would be the native-hardware targets for the port (would need kernel support implemented, but it's technically possible). I find dealing with memory management issues on 32bit architectures a pain. There is never enough address space. > > As far as 64-bit CPUs go, POWER7 is the first one that could in practice run the current ppc64le configuration, but in glibc it's limited to POWER8 and in gcc the default for powerpc64le is also POWER8 (however, it is perfectly possible to configure gcc for POWER7 and use musl libc with it). That's interesting. I guess I was tricked but the glibc limitation. Thanks Michal