[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d70b0b48-b4bf-293b-24eb-1eadfcb90f34@loongson.cn>
Date: Sun, 29 Jan 2023 09:15:11 +0800
From: 王洪亮 <wanghongliang@...ngson.cn>
To: musl@...ts.openwall.com
Subject: Re: add loongarch64 port v6.
Hi,
Is there anything else that needs to be modified in patch v6?
I'm Looking forward to your reply,thanks.
Hongliang Wang.
在 2023/1/9 下午5:46, 王洪亮 写道:
> Hi,
>
> Is there anything else that needs to be modified in patch v6?
>
> I'm Looking forward to your reply,thanks.
>
> Hongliang Wang.
>
>
> 在 2022/12/19 下午2:32, 王洪亮 写道:
>> Hi,
>>
>> 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.
>>
>> Hongliang Wang.
>>
>>
>> 在 2022/11/15 下午3:17, 王洪亮 写道:
>>> Hi,
>>>
>>> I published loongarch64 port v6 in
>>> https://github.com/loongson/musl/tree/loongarch-v3.0
>>>
>>> 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
>>> effects.
>>> 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 [0] is not valid C. it is not standard in
>>> musl,so use
>>> extcontext[] instead of extcontext[0].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.
>>>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
