From: Jeffrey Walton Subject: Re: [PATCH RFC 0/3] API for 128-bit IO access Date: Wed, 24 Jan 2018 11:38:42 -0500 Message-ID: References: <20180124090519.6680-1-ynorov@caviumnetworks.com> Reply-To: noloader@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, LKML , Linux Crypto Mailing List , Al Viro , Andrew Morton , Andrew Pinski , Arnd Bergmann , Catalin Marinas , "David S . Miller" , Geethasowjanya Akula , Greg Kroah-Hartman , Ingo Molnar , Kees Cook , Laura Abbott , Nicholas Piggin , Sunil Goutham , Will Deacon To: Yury Norov Return-path: In-Reply-To: <20180124090519.6680-1-ynorov@caviumnetworks.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Wed, Jan 24, 2018 at 4:05 AM, Yury Norov 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