From: Steven Munroe <munroesj@linux.vnet.ibm.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
"Cownie, James H" <james.h.cownie@intel.com>,
nd@arm.com,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: [patch] getauxval.3 correct AT_HWCAP result description
Date: Thu, 04 Aug 2016 15:35:43 -0500 [thread overview]
Message-ID: <1470342943.15257.1.camel@oc7878010663> (raw)
In-Reply-To: <5785F835.4070209@arm.com>
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.
prev parent reply other threads:[~2016-08-04 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 16:35 [patch] getauxval.3 correct AT_HWCAP result description Cownie, James H
2016-07-12 20:24 ` Michael Kerrisk (man-pages)
2016-07-13 8:13 ` Szabolcs Nagy
[not found] ` <5785F835.4070209-5wv7dgnIgG8@public.gmane.org>
2016-07-13 8:34 ` Cownie, James H
[not found] ` <397D95928DECEF49983F5B237627E97857330926-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-07-14 6:44 ` Michael Kerrisk (man-pages)
2016-08-04 20:35 ` Steven Munroe [this message]
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=1470342943.15257.1.camel@oc7878010663 \
--to=munroesj@linux.vnet.ibm.com \
--cc=james.h.cownie@intel.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=nd@arm.com \
--cc=szabolcs.nagy@arm.com \
/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