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.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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 2675 invoked from network); 12 Apr 2021 10:39:19 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 12 Apr 2021 10:39:19 -0000 Received: (qmail 23817 invoked by uid 550); 12 Apr 2021 10:39:17 -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 23796 invoked from network); 12 Apr 2021 10:39:16 -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; bh=vTuvWeWQ8yWRtMYEtP57jJ50l2YnjeAhRczZQXKl71A=; b=ZiHeJ0RhdITh/i8qS7slA5MI4fcGdfDDMyX6a9t0LaTSEza1eC4Z0/zm/GhX5md9cz 8qOUE6ZwnS1ZYp6EGxRaCi8PgKXB/LnMPZbirBT0l4t5fgJBPt/IF5QunIlnGzgrV766 KmelJRlAr/+8UWVs8vA6sSPZdDfr2fRYKVUIJdH2RyNTIfp+iRFM96IegQWkyQ+eZ17W YcgfxaIUuE783dSRvdtGIudnDAgPMi2QS5iUBaVISfW1vhgqJVUmOuB2y3IySrrxjR41 y/PcTxhuMMlCxmHXM7YsSiaXzgPWjuasWvzpIuh5wAZShvBS5SmfxyEuBc5/g6U8BhYH 5H+A== 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; bh=vTuvWeWQ8yWRtMYEtP57jJ50l2YnjeAhRczZQXKl71A=; b=Oxinmx3HWrIqjwZaMjO+fTwKBerSY8qP3o+FvUWCfnRQIZZEb+z2prYfrOxP0s9E8W 4NsermPwwHF8gWNBiQvsrXM4+XGlLPyCxQUu/7/NsJ4QpQcoygRSdJX3q0TNGySrCu9z 6aouP06bmgbiXDWz17AnEEwjSKNtC+50mPpyqNUdserRuTL5039bGPxBWKo1HiOhSNbu q9Baw9SZHLlWehqk/+C4//BCF6rO2gUvR8CQyX+r6qMWiBeHLfJYypvzl5McSEvwRfbl ey/jyCkLuNP0T42rWXEiBhBo/sqQEMjdQpQrFqtI0/epg3zDL9BEzuDrgkTBbc9qQaeV uhtA== X-Gm-Message-State: AOAM5339/sERFyRiWmEohlvZJ+87K5QbksFWKep8Fl82ZBVo4CsHQ6A8 Vlx1PRE2wjSjky5Ul+DfNxdsnatIukrJ+LqNI6FdHsTrt5Y= X-Google-Smtp-Source: ABdhPJw5GlXQKwdABZKFzXlRDaOxicPVSRWffoj5lUgIDyW6sKqAKglxezg+neC6PEfHMmk0JOkj13sfCkcdi0quAg0= X-Received: by 2002:a05:6638:3048:: with SMTP id u8mr27475786jak.91.1618223944583; Mon, 12 Apr 2021 03:39:04 -0700 (PDT) MIME-Version: 1.0 References: <20210410122449.GH2799122@port70.net> In-Reply-To: From: Nagakamira Date: Mon, 12 Apr 2021 13:38:53 +0300 Message-ID: To: musl@lists.openwall.com Content-Type: multipart/alternative; boundary="000000000000624f1905bfc41f86" Subject: Re: [musl] Linux distribution for using RISC-V musl? --000000000000624f1905bfc41f86 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable lto on riscv64 is broken I will revert the commit when I will have free time and make it work =D0=BF=D0=BD, 12 =D0=B0=D0=BF=D1=80. 2021 =D0=B3., 13:30 ardi : > Ataraxia looks really interesting: LLVM+musl+Toybox is the kind of > distribution I=E2=80=99d love to have. Is there any page explaining how t= o install > Ataraxia on RISCV? The docs only cover x86 and PPC, and besides the lates= t > RISCV release I found is from 2019 or so... > > Also, regarding LLVM LTO, what=E2=80=99s the ticket for following that bu= g? I > searched for it and all what I found is. > > Thanks!! > > > Nagakamira wrote: > >> Try ataraxia gnu/linux! But llvm lto have to be fixed. >> >> =D0=B2=D1=81, 11 =D0=B0=D0=BF=D1=80. 2021 =D0=B3., 00:17 ardi : >> >>> Really useful!! Thanks a lot! >>> >>> On Sat, Apr 10, 2021 at 2:24 PM Szabolcs Nagy wrote: >>> > >>> > * ardi [2021-04-10 14:08:31 +0200]: >>> > > Also, I've read that QEMU is able to emulate multicore RISC-V CPUs. >>> > > Does musl support multicore RISC-V in 64bit? I mean, if I configure= a >>> > > multicore RISC-V in QEMU and I try to build a parallel loop using >>> > > OpenMP for example, will such loop be parallelized if I'm using mus= l? >>> > >>> > yes. >>> > >>> > this has not much to do with the libc though. >>> > openmp uses pthreads, pthreads uses clone and >>> > clone is implemented by the os in some way. >>> > whether things are parallel is not in the hands >>> > of the libc and the logic is not target dependent, >>> > the libc works the same way on x86_64 as on riscv. >>> > there can be target specific synchronization bugs >>> > in the libc, but those are just bugs. >>> > >>> >> --000000000000624f1905bfc41f86 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
lto on riscv64 is broken I will revert the commit when I = will have free time and make it work

=D0=BF=D0=BD, 12 =D0=B0=D0=BF=D1=80. 20= 21 =D0=B3., 13:30 ardi <ar= dillasdelmonte@gmail.com>:
<= div dir=3D"auto">Ataraxia looks really interesting: LLVM+musl+Toybox is the= kind of distribution I=E2=80=99d love to have. Is there any page explainin= g how to install Ataraxia on RISCV? The docs only cover x86 and PPC, and be= sides the latest RISCV release I found is from 2019 or so...

Also, regarding LLVM LTO, what=E2=80= =99s the ticket for following that bug? I searched for it and all what I fo= und is.=C2=A0

Thanks!!


Nagakamira <nagakamira@gmail.com>= ; wrote:
Try atar= axia gnu/linux! But llvm lto have to be fixed.

=D0=B2=D1=81, 11 =D0=B0=D0=BF= =D1=80. 2021 =D0=B3., 00:17 ardi <ardillasdelmonte@gmail.com= >:
Really useful!! Thanks a lot!

On Sat, Apr 10, 2021 at 2:24 PM Szabolcs Nagy <nsz@port70.net= > wrote:
>
> * ardi <ardillasdelmonte@gmail.com> [2021= -04-10 14:08:31 +0200]:
> > Also, I've read that QEMU is able to emulate multicore RISC-V= CPUs.
> > Does musl support multicore RISC-V in 64bit? I mean, if I configu= re a
> > multicore RISC-V in QEMU and I try to build a parallel loop using=
> > OpenMP for example, will such loop be parallelized if I'm usi= ng musl?
>
> yes.
>
> this has not much to do with the libc though.
> openmp uses pthreads, pthreads uses clone and
> clone is implemented by the os in some way.
> whether things are parallel is not in the hands
> of the libc and the logic is not target dependent,
> the libc works the same way on x86_64 as on riscv.
> there can be target specific synchronization bugs
> in the libc, but those are just bugs.
>
--000000000000624f1905bfc41f86--