From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>, arnd@arndb.de
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] m68k: use kernel's generic muldi3 libgcc function
Date: Wed, 6 Nov 2024 08:04:44 +1000 [thread overview]
Message-ID: <1dd8be4b-d5c3-4074-a91e-3ce998ce3050@linux-m68k.org> (raw)
In-Reply-To: <CAMuHMdVZh6-64hfx1jgOijBEG6cTftinqf+4fZvqjJtV1hO95g@mail.gmail.com>
Hi Geert,
On 5/11/24 21:46, Geert Uytterhoeven wrote:
> Hi Greg, Arnd,
>
> On Mon, Nov 13, 2023 at 2:32 PM Greg Ungerer <gerg@linux-m68k.org> wrote:
>> Use the kernels own generic lib/muldi3.c implementation of muldi3 for
>> 68K machines. Some 68K CPUs support 64bit multiplies so move the arch
>> specific umul_ppmm() macro into a header file that is included by
>> lib/muldi3.c. That way it can take advantage of the single instruction
>> when available.
>>
>> There does not appear to be any existing mechanism for the generic
>> lib/muldi3.c code to pick up an external arch definition of umul_ppmm().
>> Create an arch specific libgcc.h that can optionally be included by
>> the system include/linux/libgcc.h to allow for this.
>>
>> Somewhat oddly there is also a similar definition of umul_ppmm() in
>> the non-architecture code in lib/crypto/mpi/longlong.h for a wide range
>> or machines. Its presence ends up complicating the include setup and
>> means not being able to use something like compiler.h instead. Actually
>> there is a few other defines of umul_ppmm() macros spread around in
>> various architectures, but not directly usable for the m68k case.
>>
>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
>
> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
>> arch/Kconfig | 8 +++
>> arch/m68k/Kconfig | 2 +
>> arch/m68k/include/asm/libgcc.h | 20 +++++++
>> arch/m68k/lib/Makefile | 2 +-
>> arch/m68k/lib/muldi3.c | 97 ----------------------------------
>> include/linux/libgcc.h | 4 ++
>> 6 files changed, 35 insertions(+), 98 deletions(-)
>> create mode 100644 arch/m68k/include/asm/libgcc.h
>> delete mode 100644 arch/m68k/lib/muldi3.c
>
> I had this in my local tree for about a year.
> Is it fine to queue this in the m68k tree, or does this need a broader
> coverage?
I am still in favor of it :-)
Would be good to get some feedback on the common code changes, like the change
to libgcc.h.
Regards
Greg
next prev parent reply other threads:[~2024-11-05 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 13:32 Greg Ungerer
2024-11-05 11:46 ` Geert Uytterhoeven
2024-11-05 22:04 ` Greg Ungerer [this message]
2024-12-02 1:34 ` Greg Ungerer
2024-12-02 9:27 ` Arnd Bergmann
2024-12-09 12:32 ` Geert Uytterhoeven
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=1dd8be4b-d5c3-4074-a91e-3ce998ce3050@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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®