From: Vineet Gupta <vgupta@kernel.org>
To: linux-snps-arc@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Dinh Nguyen <dinguyen@kernel.org>,
Simon Schuster <schuster.simon@siemens-energy.com>,
Vineet Gupta <vgupta@kernel.org>
Subject: [PATCH 0/4] Remove libgcc dependency for ARC
Date: Wed, 18 Nov 2026 21:59:54 -0800 [thread overview]
Message-ID: <20261119055958.1621709-1-vgupta@kernel.org> (raw)
Hi,
Arnd pestered me to do this.
Most of the generic emulation routines were present in lib/ flready.
Thanks to Dinh Nguyen and Simon Schuster for filling in the rest.
Thx,
-Vineet
Vineet Gupta (4):
ARC: math emul: elide 64/64 divide and floating point routines
ARC: math emul: use existing lib versions of libgcc routines
Revert "ARC: Strip libgcc debug information when generating BTF"
ARC: stop linking libgcc
arch/arc/Kconfig | 10 ++++++++++
arch/arc/Makefile | 9 ---------
arch/arc/kernel/arcksyms.c | 37 -------------------------------------
arch/arc/lib/Makefile | 8 --------
4 files changed, 10 insertions(+), 54 deletions(-)
--
2.53.0
WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <vgupta@kernel.org>
To: linux-snps-arc@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Dinh Nguyen <dinguyen@kernel.org>,
Simon Schuster <schuster.simon@siemens-energy.com>,
Vineet Gupta <vgupta@kernel.org>
Subject: [PATCH 0/4] Remove libgcc dependency for ARC
Date: Wed, 18 Nov 2026 21:59:54 -0800 [thread overview]
Message-ID: <20261119055958.1621709-1-vgupta@kernel.org> (raw)
Hi,
Arnd pestered me to do this.
Most of the generic emulation routines were present in lib/ flready.
Thanks to Dinh Nguyen and Simon Schuster for filling in the rest.
Thx,
-Vineet
Vineet Gupta (4):
ARC: math emul: elide 64/64 divide and floating point routines
ARC: math emul: use existing lib versions of libgcc routines
Revert "ARC: Strip libgcc debug information when generating BTF"
ARC: stop linking libgcc
arch/arc/Kconfig | 10 ++++++++++
arch/arc/Makefile | 9 ---------
arch/arc/kernel/arcksyms.c | 37 -------------------------------------
arch/arc/lib/Makefile | 8 --------
4 files changed, 10 insertions(+), 54 deletions(-)
--
2.53.0
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next reply other threads:[~2026-11-19 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 5:59 Vineet Gupta [this message]
2026-11-19 5:59 ` [PATCH 0/4] Remove libgcc dependency for ARC Vineet Gupta
2026-11-19 5:59 ` [PATCH 1/4] ARC: math emul: elide 64/64 divide and floating point routines Vineet Gupta
2026-11-19 5:59 ` Vineet Gupta
2026-11-19 5:59 ` [PATCH 2/4] ARC: math emul: use existing lib versions of libgcc routines Vineet Gupta
2026-11-19 5:59 ` Vineet Gupta
2026-11-19 5:59 ` [PATCH 3/4] Revert "ARC: Strip libgcc debug information when generating BTF" Vineet Gupta
2026-11-19 5:59 ` Vineet Gupta
2026-11-19 5:59 ` [PATCH 4/4] ARC: stop linking libgcc Vineet Gupta
2026-11-19 5:59 ` Vineet Gupta
2026-11-19 7:35 ` [PATCH 0/4] Remove libgcc dependency for ARC Arnd Bergmann
2026-11-19 7:35 ` 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=20261119055958.1621709-1-vgupta@kernel.org \
--to=vgupta@kernel.org \
--cc=arnd@arndb.de \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.