[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALW65jZvieqvHei31Ufikz4SVEGvDZwGyLGf=9Myqw1hS9m-sg@mail.gmail.com>
Date: Thu, 17 Apr 2025 15:45:03 +0800
From: Qingfang Deng <dqfext@...il.com>
To: noloader@...il.com
Cc: Ard Biesheuvel <ardb@...nel.org>, Eric Biggers <ebiggers@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>,
Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>, linux-crypto@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
Christoph Müllner <christoph.muellner@...ll.eu>,
Qingfang Deng <qingfang.deng@...lower.com.cn>
Subject: Re: [RFC PATCH] crypto: riscv: scalar accelerated GHASH
Hi Jeffrey,
On Thu, Apr 17, 2025 at 3:40 PM Jeffrey Walton <noloader@...il.com> wrote:
>
> On Thu, Apr 17, 2025 at 3:25 AM Qingfang Deng <dqfext@...il.com> wrote:
> >
> > Hi Ard,
> >
> > On Thu, Apr 17, 2025 at 2:58 PM Ard Biesheuvel <ardb@...nel.org> wrote:
> > > [...]
> > >
> > > Also, do you need to test for int128 support? Or is that guaranteed
> > > for all compilers that are supported by the RISC-V port?
> >
> > I believe int128 support is available for all 64-bit targets.
>
> You can verify the compiler supports int128 with the following macro:
>
> #if (__SIZEOF_INT128__ >= 16)
> ...
> #endif
>
> Also see <https://gcc.gnu.org/pipermail/gcc-help/2015-August/124862.html>.
There is a Kconfig symbol ARCH_SUPPORTS_INT128. I may switch to that.
>
> Jeff
Powered by blists - more mailing lists