Hi helmut,
Nice to communicate with you on RPC.
First, helmut means,
I think one of the early bootstrap failures is around libanl/libutil. do you
think loong* should ship with those stub libraries or not?
I see that in your rebootstrap fork, you opt for not having libanl/libutil (in
a crappy way). that's fine in principle, but check the codesearches to get an
idea of how many packages you will have to patch then.the other option is to
patch glibc to include those static stub libraries and let it work like before.
The most pressing tasks，
a) create a dpkg bug for the architecture.
b) submit the multilib-multiarch stuff to gcc packaging.
c) figure out how to deal with -lanl/-lutil.
Second, about the employee relations.
zhangjial...@loongson.cn,sangm...@loongson.cn,zhangdan...@loongson.cn,We are
colleagues，our leader is wanghon...@loongson.cn. And aim to port to loongarch
for debian.
Sincerely，thanks for helmut’s suggestions. And I have two questions want to
discuss.
One, if bootstrap of debian lastest version need libanl/libutil library?
The other, glibc upstream seems to have encoded the rule: any architecture that
is first released as glibc 2.34 or later. In this case, glibc upstream is not
available libanl/libutil library.
Whether we want to stick to that or as glibc? Needing to discuss.
Thankfully, debian community and our team all favour with loong64(loong32) for
dpkg.
Finally, I need to create a dpkg bug for our architecture as fast as, which is
useful for Mr. helmut to pull request about
https://salsa.debian.org/helmutg/rebootstrap.
Thanks!
-----原始邮件-----
发件人:"张丹丹" <zhangdan...@loongson.cn>
发送时间:2022-11-03 20:11:15 (星期四)
收件人: debian-devel@lists.debian.org, hel...@subdivi.de
抄送:
主题: 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 discuss the port with the community and send
an email to the debian-devel mailing list.
1、Introduction
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
2、Links from upstream
Kernel、Gcc、Gdb、Binutils、Glibc、Llvm、Golang have merged by upstream(github)
projects and so on.
For examples,
Kernel : https://www.kernel.org/doc/html/latest/
Gcc: https://gcc.gnu.org/gcc-12/changes.html
Gdb: https://sourceware.org/gdb/
Binutils:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/heads/binutils-2_39-branch
Glibc: https://sourceware.org/pipermail/libc-alpha/2022-August/141193.html
Llvm: https://github.com/llvm/llvm-project/tree/main/llvm/lib/Target
Golang: https://go.dev/doc/go1.19
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.
