Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25ec54b9.3ddd.1797a0cf8b6.Coremail.zhaixiaojuan@loongson.cn>
Date: Mon, 17 May 2021 19:19:01 +0800 (GMT+08:00)
From: 翟小娟 <zhaixiaojuan@...ngson.cn>
To: musl@...ts.openwall.com
Cc: 陈国祺 <chenguoqi@...ngson.cn>
Subject: Re: Re: Re: Re: Port the new architecture loongarch64 to
 musl

The reason for the implementation in assembly  is because I am familiar with assembly myself. I think this shows the implementation logic and final purpose of the function more  clearly than the implementation in C language.


&gt; -----原始邮件-----
&gt; 发件人: "Ariadne Conill" <ariadne@...eferenced.org>
&gt; 发送时间: 2021-05-13 03:53:01 (星期四)
&gt; 收件人: musl@...ts.openwall.com
&gt; 抄送: "陈国祺" <chenguoqi@...ngson.cn>
&gt; 主题: Re: Re: Re: [musl] Port the new architecture loongarch64 to musl
&gt; 
&gt; Hi,
&gt; 
&gt; On Wed, 12 May 2021, 翟小娟 wrote:
&gt; 
&gt; &gt; Hi,
&gt; &gt; We have ported the code of libucontext for loongarch64 architecture and can be obtained from https://github.com/loongson-community/libucontext 
&gt; &gt; Currently qemu is still being tested, I will announce it as soon as it is completed.
&gt; 
&gt; It looks alright, but I am wondering why makecontext is written in 
&gt; assembly.  The reason why it is written in assembly for mips had to do 
&gt; with specific peculariaties of how the MIPS64 ABI interacted with 
&gt; libucontext.  I don't see that the loongarch64 code is trying to capture 
&gt; the $gp register though.
&gt; 
&gt; Ariadne


</chenguoqi@...ngson.cn></ariadne@...eferenced.org>

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.