From: 王洪亮 <email@example.com>
Subject: Re: [musl] add loongarch64 port v6.
Date: Mon, 19 Dec 2022 14:32:50 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Is there anything else that needs to be modified in patch v6？
I have prepared a LoongArch machine for remote connection testing.
Please send me a private message and I reply for login and password.
I'm Looking forward to your reply,thanks.
在 2022/11/15 下午3:17, 王洪亮 写道:
> I published loongarch64 port v6 in
> Fixed the following problems:
> 1.Fixed some inappropriate comments in elf.h.
> 2.Fixed spaces and tabs used.
> 3.Removed crt/loongarch64/crti.s and crt/loongarch64/crtn.s.
> 4.Fixed the problems mentioned below email.
> There are also some unmodified problems as follows:
> 1.Whether we still implement __clone() within __NR_clone3
> syscall in LoongArch?
> In latest kernel,function clone3_stack_valid(),the condition
> of (kargs->stack_size == 0) is still valid, call __clone()
> (within __NR_clone3 syscall) is fail.
> I restore to the __NR_clone for libc-test OK temporary.
> 2.I don't remove __syscall7,I understand keep it without negative
> maybe used in the future.glibc also realize __syscall7 in LoongArch.
> 3.I don't remove arch/loongarch64/bits/ptrace.h,I'm not sure if it
> will be
> used in the future.the most architectures support it.
> 4.The definition of extcontext in mcontext_t in musl is not consistent
> with kernel,Because  is not valid C. it is not standard in musl,so use
> extcontext instead of extcontext.This question has been discussed in
> previous email named [musl] add loongarch64 port v3 in May.
> Please check first,I will prepare a physical execution environment for
> run checks.
> I'm Looking forward to your reply,thanks.
> Hongliang Wang.
next prev parent reply other threads:[~2022-12-19 6:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 8:15 [musl] add loongarch64 port v5 王洪亮
2022-09-06 1:51 ` [musl] " 王洪亮
2022-09-06 5:12 ` WANG Xuerui
2022-10-08 1:44 ` 王洪亮
2022-10-12 8:22 ` [musl] " WANG Xuerui
2022-11-15 7:17 ` [musl] add loongarch64 port v6 王洪亮
2022-12-19 6:32 ` 王洪亮 [this message]
2023-01-09 9:46 ` 王洪亮
2023-01-29 1:15 ` 王洪亮
2023-01-29 8:52 ` Ariadne Conill
2023-01-29 17:04 ` Rich Felker
2023-01-30 1:27 ` 王洪亮
2023-02-16 23:13 ` Rich Felker
2023-02-17 7:06 ` 王洪亮
2023-03-17 8:41 ` 王洪亮
2023-04-03 13:35 ` Szabolcs Nagy
2023-04-03 14:42 ` Rich Felker
2023-04-03 15:44 ` Szabolcs Nagy
2023-04-04 9:46 ` 王洪亮
2023-04-04 17:06 ` Szabolcs Nagy
2023-04-11 10:00 ` 王洪亮
2023-04-12 2:21 ` 王洪亮
2022-10-12 18:20 ` [musl] add loongarch64 port v5 Rich Felker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).