On 2021/8/12 00:39, WANG Xuerui wrote: > Hi everyone, > > <snip> > > ## Gentoo porting plans > > I'm planning to take ARCH=loongarch for the port; and support the LP64 > ABI > first. I'd like to support both LP64 and ILP32 ABIs, but that's not a > priority. > > The ABI flag might be named "ABI_LOONGARCH" but that's IMO a bit long > (pun > semi-intended); ARCH=loong and ABI_LOONG might be better, I'm open to > suggestions. > > Because much of the ABI and even some toolchain internals are going > through > VERY fierce debate and rework, obviously the port will remain > experimental > for a long time. Some minimal support should get in tree though; doing so > would ease a lot of pain for experimentation. I already hacked my way to > generate working crossdev toolchains, and is halfway towards a rootfs > with > working Python (and Portage). I've already independently ported > strace, and > plan to do the same to libffi in the coming days which would give me > Python. > > I'll do all work in my own loongson-overlay first, and upstream these > when > appropriate. Eventually I hope to have working crossdev, qemu-user > emulation > and proper catalyst support. > Some kind of "progress update": I've successfully built stage3 and minimal installation CD for ARCH=loong; ABI_LOONG is not implemented due to Loongson retracting 32-bit support themselves, this port is 64-bit only for now, and may remain so forever (depends on Loongson's intentions). All modifications are made in loongson-overlay[1]; no ad-hoc patches to main Portage tree is needed after all. My used catalyst specs are put at [2]; currently all hard-coded and no automation.
I'm going to send patches for review gradually in the following days, as the holiday here is over; however I'd like to know whether we need to wait for the upstream merge of toolchain/kernel support before we can take patches for ARCH=loong, or if there's more prerequisites. [1]: https://github.com/xen0n/loongson-overlay [2]: https://github.com/xen0n/releng/tree/loong
