From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Munroe Subject: Re: [patch] getauxval.3 correct AT_HWCAP result description Date: Thu, 04 Aug 2016 15:35:43 -0500 Message-ID: <1470342943.15257.1.camel@oc7878010663> References: <397D95928DECEF49983F5B237627E9785733058A@IRSMSX108.ger.corp.intel.com> <2b181d0f-3a50-bf18-268b-9991de75d216@gmail.com> <5785F835.4070209@arm.com> Reply-To: munroesj@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <5785F835.4070209@arm.com> To: Szabolcs Nagy Cc: "Michael Kerrisk (man-pages)" , "Cownie, James H" , nd@arm.com, "libc-alpha@sourceware.org" , "linux-man@vger.kernel.org" List-Id: linux-man@vger.kernel.org On Wed, 2016-07-13 at 09:13 +0100, Szabolcs Nagy wrote: > On 12/07/16 21:24, Michael Kerrisk (man-pages) wrote: > >> .BR AT_HWCAP > >> -A pointer to a multibyte mask of bits whose settings > >> +A four byte long bit-mask whose settings > >> indicate detailed processor capabilities. > > why is it four byte long? > > it's a long and the target abi decides how many > bits of that is used. > For platforms that support 32- and 64-bit modes, maintaining AT_HWCAP at 32-bits simplifies code portability.