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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <619015812.381816.1750274471992@privateemail.com>
Date: Wed, 18 Jun 2025 21:21:11 +0200 (CEST)
From: Marco Bonelli <marco@...eim.net>
To: Abhigyan ghosh <zscript.team.zs@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: RISC-V 32-bit debug builds reaching breaking point: too many
 symbols

(sorry for the dupe mail, forgot to hit "reply all")

> Would using split debug info earlier in the build (e.g. extracting `.debug_*` before `vmlinux.o` grows too large) help mitigate the symbol table overflow — or is the linker still forced to carry them through regardless due to reloc dependencies?

Wish I knew honestly, not sure. That is essentially what I was asking in my mail.
If I had to take a guess, I think it wouldn't matter and just move the problem
because you would still have a huge split .dwo file, but I am not 100% sure. More
smaller files could be generated (e.g. one per compilation unit) but those would
be painful to carry around.

> Also, does this behavior differ between GNU ld and LLD in your tests?

I have tested a LLVM build and while it does produce less of those annoying
symbols, the same problem persists.

--
Marco Bonelli