From: "Arnd Bergmann" <arnd@arndb.de>
To: "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, 01 Nov 2026 20:45:32 +0100 [thread overview]
Message-ID: <ca697a3c-fee0-40a9-98e6-12e24febb3b7@app.fastmail.com> (raw)
In-Reply-To: <7de128f0-4f17-4a33-9a7a-14d5bbf62e64@kernel.org>
On Sun, Nov 1, 2026, at 19:38, Vineet Gupta wrote:
> On 11/1/26 03:09, Arnd Bergmann wrote:
>>> I'm working on getting rid of libgcc linking for ARC.
>>
>> 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.
If you need this to fix the regression, I think it's fine to merge
the shared lib/*.c files for for 7.4 along with whatever you need on
top. I suspect though based on Sasha's patch, the only thing we
actually need is to stop exporting the floating point functions
so the types don't leak into btf. If you can verify that this
is the case, I would do the full conversion for both nios2
and arc in 7.5.
Arnd
next prev parent reply other threads:[~2026-11-01 19:46 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
2026-11-01 19:45 ` Arnd Bergmann [this message]
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=ca697a3c-fee0-40a9-98e6-12e24febb3b7@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrii@kernel.org \
--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 \
--cc=vgupta@kernel.org \
/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®