linux-kernel - Re: RISC-V 32-bit debug builds reaching breaking point: too many symbols

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <C90792F2-91C2-40DA-9C90-1602CFAC0FD1@gmail.com>
Date: Thu, 19 Jun 2025 11:41:40 +0530
From: Abhigyan ghosh <zscript.team.zs@...il.com>
To: marco@...eim.net
CC: linux-kernel@...r.kernel.org
Subject: Re: RISC-V 32-bit debug builds reaching breaking point: too many symbols

Hi Marco,

Thanks for the quick reply — and no worries about the dupe!

Got it. That makes sense. I was wondering if splitting earlier would help reduce linker overhead, but I see now that the .dwo files (or .dwp) would likely still carry a heavy load and relocations would remain a bottleneck.

Interesting to hear that the same behavior persists with LLVM — I guess that confirms it's more of a fundamental tooling limit than a front-end quirk.

Appreciate your input! If I end up testing with smaller compilation units or tweaking DWARF emission flags, I’ll report back.

Best regards,  
Abhigyan Ghosh  
zsml.zscript.org  
@zscript.team.zs
aghosh