From: Nagakamira <nagakamira@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Linux distribution for using RISC-V musl?
Date: Sun, 11 Apr 2021 15:38:07 +0300 [thread overview]
Message-ID: <CAEqUM+doa62oc83p-PY4ALREWBohvpDK7fKQDYRf1CcNwxuk_Q@mail.gmail.com> (raw)
In-Reply-To: <CA+fZqCVAeYZidYee-rxiQrncO8R5yzKH__8UxzJPBArFsLniZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
Try ataraxia gnu/linux! But llvm lto have to be fixed.
вс, 11 апр. 2021 г., 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 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 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.
> >
>
[-- Attachment #2: Type: text/html, Size: 1597 bytes --]
next prev parent reply other threads:[~2021-04-11 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 12:08 ardi
2021-04-10 12:24 ` Szabolcs Nagy
2021-04-10 21:17 ` ardi
2021-04-11 12:38 ` Nagakamira [this message]
2021-04-12 10:29 ` ardi
2021-04-12 10:38 ` Nagakamira
2021-04-10 14:16 ` Khem Raj
2021-04-10 21:15 ` ardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEqUM+doa62oc83p-PY4ALREWBohvpDK7fKQDYRf1CcNwxuk_Q@mail.gmail.com \
--to=nagakamira@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).