News: 0001590454

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

LoongArch LA32 Target Proposed For The GCC Compiler

([GNU] 56 Minutes Ago LoongArch 32-bit)


While [1]LoongArch 64-bit is already part of the GCC compiler for the past several years, LoongArch 32-bit is now being proposed for the GNU Compiler Collection.

Sent out today were patches proposing LoongArch 32-bit for the GCC compiler with the LoongArch32 ILP32D ABI and LoongArch32 Reduced LA32R ILP32S ABI. The ILP32 ABI ends up being similar to the 64-bit LoongArch LP64 ABI but with some minor differences.

Since earlier this year there have been [2]proposed patches for LoongArch32 for the Linux kernel . There are also out-of-tree patches for the GNU C Library, GNU Binutils, and a pached LA32 QEMU system too. While many would love to be focused on just a 64-bit world in 2025+, it looks like Loongson is having new/recent interest now in LoongArch32 after their LoongArch64 architecture has already taken off domestically.

"These series patches introduce LoongArch32(LA32) ilp32d abi and LoongArch32 Reduced(LA32R) ilp32s abi. The ilp32 abi is similar to lp64 abi, with some differences in details.

Most gcc testcasese has passed when using qemu-user."

There are [3]34 patches now out for review and consideration for this LoongArch32 target for the GCC compiler.



[1] https://www.phoronix.com/news/LoongArch-For-GCC-12

[2] https://www.phoronix.com/news/LoongArch-32-bit-Linux-uAPI

[3] https://gcc.gnu.org/pipermail/gcc-patches/2025-November/700062.html


... an anecdote from IBM's Yorktown Heights Research Center. When a
programmer used his new computer terminal, all was fine when he was sitting
down, but he couldn't log in to the system when he was standing up. That
behavior was 100 percent repeatable: he could always log in when sitting and
never when standing.

Most of us just sit back and marvel at such a story; how could that terminal
know whether the poor guy was sitting or standing? Good debuggers, though,
know that there has to be a reason. Electrical theories are the easiest to
hypothesize: was there a loose wire under the carpet, or problems with static
electricity? But electrical problems are rarely consistently reproducible.
An alert IBMer finally noticed that the problem was in the terminal's
keyboard: the tops of two keys were switched. When the programmer was seated
he was a touch typist and the problem went unnoticed, but when he stood he was
led astray by hunting and pecking.
-- "Programming Pearls" column, by Jon Bentley in CACM February 1985