New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loongarch64-linux-gnu #166
Comments
loongarch64 support was added in glibc 2.36 |
Those error indicate missing loongarch-specific logic in the zig standard library. |
system: OS: loongarchlinux Kernel:
GCC:
binutils: 2.41-3 glibc:
With this patch, the error log is as follows:
|
system: OS: loongarchlinux Kernel:
clang
glibc
The GCC toolchain provided by the system is not working, tried with llvm and clang. The command to build bootstrap
With the same patch above, it seems that it is possible to compile zig2 successfully but failed in stage 3.
|
it seems that zig itself requires However, loongarch64 does not have Maybe we should add a translation layer for |
is there a specific reason for this or is it because its simply not implemented yet in the kernel since loongarch64 is such a relatively new architecture? |
Check the syscalls here. It seems that it is not implemented in Linux kernel intentionally. And golang has an emulation implementation of |
With current patch, I think I have implemented most of the loongarch64 things needed for zig std lib. The current build command I use:
The current error output:
The backtrace of error above:
The overflow happens on stack element 18 where I guess things like |
This has been fixed. And now the error is zig2 failed to build libunwind.
|
Disabled the macro The next problem is that ld.lld having error doing relocation when linking zig binary. |
Managed to replace |
With the patch now it is possible to build a stage3 zig binary with command
With this stage3 zig binary, there is still some problem:
|
It seems that the result is the same as #164
I'm working on this patch to try to make it work.
system:
OS: loongarchlinux
GCC:
The text was updated successfully, but these errors were encountered: