[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Port to LoongArch architecture for Debian



Hi,

      I am an employee of Loongson Technology Co,Ltd.

     Port to LoongArch architecture for Debian ,now in the "Downstreaming" section in the port life-cycle according to <https://wiki.debian.org/PortsDocs/New>.
The purpose of this mail wants to d
iscuss the port with the community and send an email to the debian-devel mailing list.

1Introduction

     The LoongArch architecture (LoongArch) is an Instruction Set Architecture (ISA) that has Reduced Instruction Set Computer (RISC) style.     

   LoongArch has the typical characteristics of RISC. LoongArch instructions are of fixed size and have regular instruction formats. Most of the instructions have two source operands and one destination operand. LoongArch is a load-store architecture; this means only the load/store instructions can access memory the operands of the other instructions are within the processor core or the immediate number in the instruction opcode.

      Loongson and LoongArch documentations: https://github.com/loongson/LoongArch-Documentation


2Links from upstream

KernelGccGdbBinutilsGlibcLlvmGolang have merged by upstream(github) projects and so on.

For examples,

3、#debian-loongarch64 IRC

Have joined the #debian-bootstrap, #debian-ports and other Debian IRC channels. And have created a new #debian-loongarch64 channel.

Thanks!




本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。 
This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it. 

Reply to: