From: Abhigyan ghosh <zscript.team.zs@gmail.com>
To: marco@mebeim.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: RISC-V 32-bit debug builds reaching breaking point: too many symbols
Date: Thu, 19 Jun 2025 11:41:40 +0530 [thread overview]
Message-ID: <C90792F2-91C2-40DA-9C90-1602CFAC0FD1@gmail.com> (raw)
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
next reply other threads:[~2025-06-19 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 6:11 Abhigyan ghosh [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=C90792F2-91C2-40DA-9C90-1602CFAC0FD1@gmail.com \
--to=zscript.team.zs@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@mebeim.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®