mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 12:09:47 +0100	[thread overview]
Message-ID: <8b4688ca-db5c-4122-b616-8e3964e403f8@app.fastmail.com> (raw)
In-Reply-To: <09db4d22-2836-4656-8c6a-a7e5377710fb@kernel.org>

On Sun, Nov 1, 2026, at 02:04, Vineet Gupta wrote:
> On 10/15/26 08:40, Sasha Levin wrote:

>> diff --git a/arch/arc/lib/Makefile b/arch/arc/lib/Makefile
>> index 30158ae69fd4a..2807ee24f27e6 100644
>> --- a/arch/arc/lib/Makefile
>> +++ b/arch/arc/lib/Makefile
>> @@ -13,3 +13,11 @@ lib-$(CONFIG_ISA_ARCV2)		+=memcpy-archs-unaligned.o
>>   else
>>   lib-$(CONFIG_ISA_ARCV2)		+=memcpy-archs.o
>>   endif
>> +
>> +# libgcc can contain complex floating-point debug types unsupported by BTF.
>> +# Strip only the debug information from a local copy of the selected archive.
>> +always-$(CONFIG_DEBUG_INFO_BTF) += libgcc.a
>> +OBJCOPYFLAGS_libgcc.a := --strip-debug
>> +
>> +$(obj)/libgcc.a: $(LIBGCC) FORCE
>> +	$(call if_changed,objcopy)
>
> 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?

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.

     Arnd

  reply	other threads:[~2026-11-01 11:10 UTC|newest]

Thread overview: 6+ 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 [this message]
2026-11-01 18:38     ` Vineet Gupta
2026-11-01 19:45       ` Arnd Bergmann

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=8b4688ca-db5c-4122-b616-8e3964e403f8@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®