From: Marco Bonelli <marco@mebeim.net>
To: Abhigyan ghosh <zscript.team.zs@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RISC-V 32-bit debug builds reaching breaking point: too many symbols
Date: Wed, 18 Jun 2025 21:21:11 +0200 (CEST) [thread overview]
Message-ID: <619015812.381816.1750274471992@privateemail.com> (raw)
In-Reply-To: <5BB59D35-BFA0-43AC-939E-213925DD4869@gmail.com>
(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
next prev parent reply other threads:[~2025-06-18 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 10:55 RISC-V 32-bit debug builds reaching breaking point: too many symbols Marco Bonelli
2025-06-18 10:55 ` Marco Bonelli
2025-06-18 11:02 ` Abhigyan ghosh
2025-06-18 11:04 ` Abhigyan ghosh
2025-06-18 19:21 ` Marco Bonelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-19 6:11 Abhigyan ghosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=619015812.381816.1750274471992@privateemail.com \
--to=marco@mebeim.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zscript.team.zs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.