Add initial support for LoongArch64

[wszqkzqk]

LoongArch is a new RISC ISA developed by loongson. There are already a lot of community support and testing about it.

This PR add loong64 support to the pure C implementation. I've tested this PR on Arch Linux for Loong64 with gcc 14.2.1 (with additional patch to fix Q suffix for fp128 literals) and clang 19.1.7. Here is the log:

• sleef-build-with-gcc-loong64.log
• sleef-build-with-clang-loong64.log

I also tested it by rebasing and applying it to pytorch 2.6.0. I've tested it with some python demos and it works fine.

[shibatch]

If we decide to officially support LoongArch, then we need to keep maintaining it.
To do so, we also need to maintain a CI environment.
So far, I have taken on the work for free, but I cannot do it any more.
We need you to bear the labor and expense for this.

[wszqkzqk]

If we decide to officially support LoongArch, then we need to keep maintaining it. To do so, we also need to maintain a CI environment. So far, I have taken on the work for free, but I cannot do it any more. We need you to bear the labor and expense for this.

I cannot afford the CI since I also do my work for free. 😂😂😂 Is it possible to classify different architectures into different support levels? (Maybe keep some architectures of which test results that don't guarantee) If not, I can also try to contact Loongson to afford this.

[shibatch]

I cannot provide ongoing support for free.
If no one is willing to cover the cost, please just fork the project and support LoongArch at your repo.

[wszqkzqk]

I cannot provide ongoing support for free. If no one is willing to cover the cost, please just fork the project and support LoongArch at your repo.

Sigh. As an open source software developer, I completely understand your thoughts. But as a downstream Linux distribution maintainer without financial support, I am also unwilling to bear too much ongoing maintenance costs, so I am unwilling to fork this project. I have already told Loongson about the importance of your project, so let's wait for Loongson's response. 😊😊😊

[loongson-zn]

@shibatch Does the CI requirement strictly demand physical machines, or would QEMU‑based emulation be acceptable?

[shibatch]

Rather, since this project is underfunded, responding to any of the requests is taking time.

…

On Wed, Aug 26, 2026 at 16:13 Zhang Na ***@***.***> wrote: *loongson-zn* left a comment (shibatch/sleef#672) <#672 (comment)> @shibatch <https://github.com/shibatch> Does the CI requirement strictly demand physical machines, or would QEMU‑based emulation be acceptable? — Reply to this email directly, view it on GitHub <#672?email_source=notifications&email_token=AD2A7F36WLTT5ZOYF3WKILT5L2E2LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBSGE4DONZSGQ4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5421877248>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2A7F2VRUE6HHJVVB7HO7D5L2E2LAVCNFSNUABEKJSXA33TNF2G64TZHM2DQOJUGEYTEMZ3JFZXG5LFHMZDSNBQGM4DINRZG2QXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AD2A7F2LC4LH7C7ZROHFWDT5L2E2LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBSGE4DONZSGQ4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AD2A7FYGBPK6X5KOPL6HYQ35L2E2LA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBSGE4DONZSGQ4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[loongson-zn]

Could you please clarify what requirements or resources we need to satisfy in order to get LoongArch support merged upstream?

[shibatch]

Unlike in the past, we now conduct software development as a business. Please keep this in mind and send an email directly to my email address.

…

On Wed, Aug 26, 2026 at 16:31 Zhang Na ***@***.***> wrote: *loongson-zn* left a comment (shibatch/sleef#672) <#672 (comment)> Could you please clarify what requirements or resources we need to satisfy in order to get LoongArch support merged upstream? — Reply to this email directly, view it on GitHub <#672?email_source=notifications&email_token=AD2A7FZBJPBH3ACGTYA3A235L2G4BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBSGIYDKMJWHE2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5422051694>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2A7F3NAJ67QJT3MYDCQY35L2G4BAVCNFSNUABEKJSXA33TNF2G64TZHM2DQOJUGEYTEMZ3JFZXG5LFHMZDSNBQGM4DINRZG2QXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AD2A7F56O4EVKKKCEBA3JIT5L2G4BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBSGIYDKMJWHE2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AD2A7F4D6VKZNGROBW5CB4L5L2G4BA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNBSGIYDKMJWHE2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[arrowd]

Looking at the changes, it seems that there is no architecture-specific code being added yet.

Maybe it'd make sense to restructure the build system in such a way that building on an unsupported arch would just go the scalar path without requiring boilerplate code?