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=-1.0 required=5.0 tests=MAILING_LIST_MULTI, NICE_REPLY_A,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31235 invoked from network); 19 Dec 2022 06:33:16 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 19 Dec 2022 06:33:16 -0000 Received: (qmail 26362 invoked by uid 550); 19 Dec 2022 06:33:12 -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 26327 invoked from network); 19 Dec 2022 06:33:11 -0000 From: =?UTF-8?B?546L5rSq5Lqu?= To: musl@lists.openwall.com References: <4fd8ad44-6e64-c4f3-6f48-420cdae8c13f@loongson.cn> Message-ID: <155e9a0c-5839-01a5-f152-888bcd918529@loongson.cn> Date: Mon, 19 Dec 2022 14:32:50 +0800 User-Agent: Mozilla/5.0 (X11; Linux mips64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <4fd8ad44-6e64-c4f3-6f48-420cdae8c13f@loongson.cn> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CM-TRANSID:AQAAf8Cxf+SSBaBjT6kEAA--.19883S3 X-CM-SenderInfo: pzdqwxxrqjzxhdqjqz5rrqw2lrqou0/ X-Coremail-Antispam: 1Uk129KBjvJXoWxJr15try5uFy8WFWfWrWruFg_yoW8AFy5pF WSvF48KrW8Gr13t39rK34rWF17KrZ5tr17WF1fK3y8ury3WF95ury2kan09F9rCw1Ig3yj vry8G343XF1jyaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUj1kv1TuYvTs0mT0YCTnIWj qI5I8CrVACY4xI64kE6c02F40Ex7xfYxn0WfASr-VFAUDa7-sFnT9fnUUIcSsGvfJTRUUU bI8YFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1xkIjI8I6I8E6xAIw20EY4v20xvaj40_Wr0E3s 1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM28CjxkF64kEwVA0rcxSw2x7M28EF7xv wVC0I7IYx2IY67AKxVWUCVW8JwA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwA2z4 x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjcxK6I8E87Iv6xkF7I0E14v26r4UJVWxJr1l e2I262IYc4CY6c8Ij28IcVAaY2xG8wAqjxCEc2xF0cIa020Ex4CE44I27wAqx4xG64xvF2 IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4U McvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvEwIxGrwCYjI0SjxkI62AI1cAE67vIY487Mx AIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_Jr0_ Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUJVWUXwCIc40Y0x0EwI xGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8 JwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcV C2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxUzsqWUUUUU Subject: Re: [musl] add loongarch64 port v6. 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. >