From: Vineet Gupta <vgupta@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, Vineet Gupta <vgupta@kernel.org>,
Sasha Levin <sashal@kernel.org>,
linux-snps-arc@lists.infradead.org
Cc: Andrii Nakryiko <andrii@kernel.org>,
Ilya Leoshkevich <iii@linux.ibm.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
"schuster.simon@siemens-energy.com"
<schuster.simon@siemens-energy.com>
Subject: Re: [PATCH] ARC: Strip libgcc debug information when generating BTF
Date: Sun, 1 Nov 2026 10:38:57 -0800 [thread overview]
Message-ID: <7de128f0-4f17-4a33-9a7a-14d5bbf62e64@kernel.org> (raw)
In-Reply-To: <8b4688ca-db5c-4122-b616-8e3964e403f8@app.fastmail.com>
On 11/1/26 03:09, Arnd Bergmann wrote:
>> I'm working on getting rid of libgcc linking for ARC.
>> This requires adding some GENERIC_LIB_* routines, but as part of that
>> series I'll propose a revert of this and then the dropping the first link.
>> Don't intend to revert this per se, but revert just makes it cleaner.
> Have you seen Simon's series?
No I didn't until now.
> https://lore.kernel.org/all/20261030-nios2-remove-usage-of-libgcc-v1-3-4e341c66082e@siemens-energy.com/
>
> I hope there is some overlap with what you need for arc in the
> lib/*.c functions. I can take both through the asm-generic tree
> to reduce the dependencies if that helps.
Oh that fits the bill perfectly. Mine also switched the others (with
build test using their cross tool-chains).
Anyhow I'll wait for that to land. Would this need to wait full cycle ?
If it can land in 7.4-rcX, I can hold off my existing patches for
switching to current in-tree lib/* to also use the new ones and be done
with libgcc.
Thx,
-Vineet
next prev parent reply other threads:[~2026-11-01 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 15:40 Sasha Levin
2026-10-16 9:18 ` Alan Maguire
2026-11-01 1:04 ` Vineet Gupta
2026-11-01 11:09 ` Arnd Bergmann
2026-11-01 18:38 ` Vineet Gupta [this message]
2026-11-01 19:45 ` Arnd Bergmann
2026-11-02 2:46 ` Vineet Gupta
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=7de128f0-4f17-4a33-9a7a-14d5bbf62e64@kernel.org \
--to=vgupta@kernel.org \
--cc=andrii@kernel.org \
--cc=arnd@arndb.de \
--cc=bpf@vger.kernel.org \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=sashal@kernel.org \
--cc=schuster.simon@siemens-energy.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 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®