From: Arnd Bergmann <firstname.lastname@example.org> To: email@example.com Subject: Re: [musl] Re: add loongarch64 port v3 Date: Wed, 11 May 2022 18:08:21 +0200 [thread overview] Message-ID: <CAK8P3a2Y5bUGYe6V05UQPkrPobs=JqCVSWWvnLcrnXyPGhbQXQ@mail.gmail.com> (raw) In-Reply-To: <20220511133707.GF7074@brightrain.aerifal.cx> On Wed, May 11, 2022 at 5:57 PM Rich Felker <firstname.lastname@example.org> wrote: > > On Mon, May 09, 2022 at 09:34:59AM +0800, 王洪亮 wrote: > > > > 在 2022/5/5 上午11:21, 王洪亮 写道: > > >Hi, > > > > > >I published loongarch64 port v3 in > > >https://github.com/loongson/musl/tree/loongarch-v2.0. > > > > > >fixed two problem: > > > > > >1.use __NR_clone3 in __clone(). > > > > > >2.remove __NR_fstat and __NR_newfstatat. > > > > > >please code review if there are any other problems ? thanks. > > > > > > > > >Hongliang Wang. > > > > > Hi, > > > > this port has any other problems need to fix? > > I'm at least waiting for confirmation from the kernel side that > everything is okay with syscall usage to move forward. I'll try to > look over the rest again soon to check that there are no remaining > issues. Since musl is using clone3 internally and no longer exports the __NR_fstat/newfstatat macros, that part is fine. The clone() one still isn't correct I think, as the mainline kernel does not yet support the emulation with a zero-length stack length. Once we add that part, musl should be fine, but then the __NR_clone definition is mismatched, as the kernel won't provide that call to user applications any more. Arnd
next prev parent reply other threads:[~2022-05-11 16:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-05 3:21 [musl] " 王洪亮 2022-05-09 1:34 ` [musl] " 王洪亮 2022-05-11 13:37 ` Rich Felker 2022-05-11 16:08 ` Arnd Bergmann [this message] 2022-05-16 14:27 ` [musl] " Rich Felker 2022-05-21 6:38 ` 王洪亮 2022-05-21 8:22 ` Markus Wichmann 2022-05-24 9:08 ` 王洪亮 2022-05-24 12:32 ` Rich Felker 2022-05-25 10:08 ` 王洪亮 2022-05-25 12:32 ` Rich Felker 2022-05-26 3:07 ` 王洪亮 2022-05-29 6:34 ` Szabolcs Nagy
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='CAK8P3a2Y5bUGYe6V05UQPkrPobs=JqCVSWWvnLcrnXyPGhbQXQ@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [musl] Re: add loongarch64 port v3' \ /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
Code repositories for project(s) associated with this 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).