I’ve heard that the latest Loongson cores are competitive per clock with the top-of-the-line x86-64 models. Is it based closely on the MIPS instruction set or has the LoongArch deviated and become its own?
In February 2021, Prestige Century Investments Limited and CIP United Company Limited (Shanghai Xinlianxin Intelligent Technology Co., Ltd.) initiated an arbitration with the Hong Kong International Arbitration Centre regarding the dispute over the MIPS technology licensing contract with Loongson Technology Corporation Limited. Ultimately, the Hong Kong International Arbitration Centre ruled that Xinlianxin is the losing party.
I see. I learned MIPS assembly langauge at Minnesota State University so I wondered about that. There isn’t much I can do with a Chinese architecture since I live in the U.S.A. but thanks for the update.
at line 6170 I can see that isl_test_cpp failed to link during gcc build. But there are no errors from the linker. Same thing again at line 12936. That looks like the first thing to understand and fix?
I see that you are running jam without the -q option, which means even if an error occurs, it will continue and try to build as much things as possible. This may make it harder to see the errors, with -q, jam will stop a bit earlier when a problem occurs and you can then fix it before moving on.
I see that you have tried to build both bootstrap and non-bootstrap builds, I’m not sure if that’s going to work well. Usually I keep the two separate in different generated directories.
Does your toolchain support PE format import/export capabilities (__declspec(dllimport))? I see, you have EDK2, which uses PE, but it doesn’t use importing/exporting, so asking.
This is great, but unfortunately Gitee requires an account for even basic features such as viewing commit history and downloading repos as ZIP archives. Would you be open to reuploading your work to another Git forge? If GitHub is not an option, perhaps Codeberg could be a more amenable choice.
hmmm, because the connection to github is not very good, I made a mirror for haiku’s repos to gitee. I will push my repos back to github today ,thanks for your advice.
They are in Haiku sources in src/system/glue/arch/
Did you fill that in and adjust he corresponding jamfiles already so your files are built?
The ld command is then run inside haikuporter, which is set up to make these files available as needed. I’m not sure you can run the same command outside of that environment.
All those are supposed to be built as part of Haiku itself, during the “stage 0” bootstrap. The build system creates a haiku_cross_devel_sysroot_stage0_<ARCH>.hpkg which should contain them.
,thanks for your advice.
