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: Mon, 02 Nov 2026 08:43:43 +0100 [thread overview]
Message-ID: <9502ed84-cb6c-448c-95bd-03c0bfab4e03@app.fastmail.com> (raw)
In-Reply-To: <adeb8dc8-1cc9-4297-8d34-3f4b0e2f4e8e@kernel.org>
On Mon, Nov 2, 2026, at 03:46, Vineet Gupta wrote:
> On 11/1/26 11:45, Arnd Bergmann wrote:
>> 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.
>
> Yeah Sasha's fix works w/o eliding the FP routines (there's an unrelated
> issue which I send a fix for [1])
>
> As of 7.4-rc1, I have 2 ARC only changes to
> 1. Switch to existing in-tree GENERIC_LIB*
> 2. Dropping FP symbols
>
> I can post them now. Once Simon's changes land, lefover ARC conversion
> and and removal of libgcc can all go together via your tree if that's OK
> with you.
Sounds good to me,
Arnd
prev parent reply other threads:[~2026-11-02 7:44 UTC|newest]
Thread overview: 8+ 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
2026-11-02 2:46 ` Vineet Gupta
2026-11-02 7:43 ` Arnd Bergmann [this message]
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=9502ed84-cb6c-448c-95bd-03c0bfab4e03@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®