[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH8yC8nvD-CWt9eZ_CumwtVB0xAKKD1uosftAKGvxrhJhcneNw@mail.gmail.com>
Date: Wed, 24 Jan 2018 11:38:42 -0500
From: Jeffrey Walton <noloader@...il.com>
To: Yury Norov <ynorov@...iumnetworks.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-arch@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrew Pinski <Andrew.Pinski@...ium.com>,
Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
"David S . Miller" <davem@...emloft.net>,
Geethasowjanya Akula <Geethasowjanya.Akula@...ium.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ingo Molnar <mingo@...nel.org>,
Kees Cook <keescook@...omium.org>,
Laura Abbott <labbott@...hat.com>,
Nicholas Piggin <npiggin@...il.com>,
Sunil Goutham <Sunil.Goutham@...ium.com>,
Will Deacon <will.deacon@....com>
Subject: Re: [PATCH RFC 0/3] API for 128-bit IO access
On Wed, Jan 24, 2018 at 4:05 AM, Yury Norov <ynorov@...iumnetworks.com> wrote:
>
> ...
> With all that, this example code:
>
> static int __init 128bit_test(void)
> {
> __uint128_t v;
> __uint128_t addr;
> __uint128_t val = (__uint128_t) 0x1234567890abc;
> ...
In case it matters, you can check for GCC support of the 128-bit types
in userland with:
#if (__SIZEOF_INT128__ >= 16)
...
#endif
Also see https://gcc.gnu.org/ml/gcc-help/2015-08/msg00185.html .
Jeff
Powered by blists - more mailing lists