From: "Arnd Bergmann" <arnd@arndb.de>
To: "Vineet Gupta" <vgupta@kernel.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"schuster.simon@siemens-energy.com"
<schuster.simon@siemens-energy.com>,
"Ley Foon Tan" <lftan@altera.com>
Cc: linux-kernel@vger.kernel.org, "kernel test robot" <lkp@intel.com>,
linux-snps-arc@lists.infradead.org, linux-parisc@vger.kernel.org,
"linux-openrisc@vger.kernel.org" <linux-openrisc@vger.kernel.org>
Subject: Re: [PATCH] nios2: ksyms: Declare __mulsi3 export
Date: Sun, 01 Nov 2026 12:19:34 +0100 [thread overview]
Message-ID: <cf2a83ea-5e5a-42c2-905b-199a43b6341a@app.fastmail.com> (raw)
In-Reply-To: <e9f9ac85-442a-4bcc-8ec6-a03a6519178d@kernel.org>
On Sun, Nov 1, 2026, at 01:26, Vineet Gupta wrote:
> On 10/31/26 16:57, Vineet Gupta wrote:
>>
>> ┌───────────┬───────┬───────────┐
>> │ routine │ calls │ functions │
>> ├───────────┼───────┼───────────┤
>> │ __udivsi3 │ 415 │ 238 │
>> ├───────────┼───────┼───────────┤
>> │ __umodsi3 │ 203 │ 131 │
>> ├───────────┼───────┼───────────┤
>> │ __divsi3 │ 77 │ 57 │
>> ├───────────┼───────┼───────────┤
>> │ __modsi3 │ 41 │ 33 │
>> └───────────┴───────┴───────────┘
>>
>> I can take a stab at providing the generic libgcc implementation in
>> lib/* but I only expect the arches using libgcc version to switch.
>
> It seems there 4 are always needed together or not at all.
> Do we want 4 Kconfig gates or just one will suffice ?
Either way is fine for me. Simon did separate symbols in his
nios2 patch[1], and I don't mind staying with that version
unless someone else feels strongly about it.
I would however like to have separate patches to add lib/divmul.c
and lib/mulsi3.c, and then patches on top that start using these
from nios2 and arc.
Arnd
[1] https://lore.kernel.org/all/20261030-nios2-remove-usage-of-libgcc-v1-3-4e341c66082e@siemens-energy.com/
prev parent reply other threads:[~2026-11-01 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 9:49 Thomas Weißschuh
2026-10-19 11:16 ` Arnd Bergmann
2026-10-19 14:34 ` Dinh Nguyen
2026-10-20 9:40 ` David Laight
2026-10-31 23:57 ` Vineet Gupta
2026-11-01 0:26 ` Vineet Gupta
2026-11-01 11:19 ` 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=cf2a83ea-5e5a-42c2-905b-199a43b6341a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dinguyen@kernel.org \
--cc=lftan@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=lkp@intel.com \
--cc=schuster.simon@siemens-energy.com \
--cc=thomas.weissschuh@linutronix.de \
--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®