From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add support for Half precision floating point
Date: Tue, 26 Jan 2016 16:21:43 +0000 [thread overview]
Message-ID: <56A79D17.2000009@arm.com> (raw)
In-Reply-To: <20160126160257.GB28238@arm.com>
On 26/01/16 16:02, Will Deacon wrote:
> Hi Suzuki,
>
> On Tue, Jan 26, 2016 at 03:52:46PM +0000, Suzuki K Poulose wrote:
>> ARMv8.2 extensions [1] include an optional feature, which supports
>> half precision(16bit) floating point/asimd data processing
>> instructions. This patch adds support for detecting and exposing
>> the same to the userspace via HWCAPs
>> +#define HWCAP_FPHP (1 << 9)
>> +#define HWCAP_ASIMDHP (1 << 10)
>
> Where did we get to with the mrs trapping you proposed here?
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/374609.html
We are yet to get some feedback from glibc/gcc folks. Siddhesh was looking
to make use of it [2]. But haven't heard anything back. Ramana mentioned
(in private) that they had some plans to take a look at it.
>
> At some point, we need to consider whether or not we want to continue
> adding new HWCAPs or whether your suggestion above is actually useful
> to userspace.
Definitely.
> Did the libc guys get anywhere with a prototype? What do we need to do
> to make progress with it?
I am not sure.
Siddesh, Ramana,
Could you please let us know your plans ?
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/381422.html
Thanks
Suzuki
next prev parent reply other threads:[~2016-01-26 16:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 15:52 [PATCH] arm64: Add support for Half precision floating point Suzuki K Poulose
2016-01-26 16:02 ` Will Deacon
2016-01-26 16:11 ` Catalin Marinas
2016-01-28 16:00 ` Will Deacon
2016-02-16 11:48 ` Szabolcs Nagy
2016-02-16 11:53 ` Will Deacon
2016-02-16 12:57 ` Szabolcs Nagy
2016-01-26 16:21 ` Suzuki K. Poulose [this message]
2016-01-26 16:55 ` Siddhesh Poyarekar
2016-01-28 16:07 ` Will Deacon
2016-01-28 16:46 ` Siddhesh Poyarekar
2016-01-28 17:27 ` Catalin Marinas
2016-01-28 17:44 ` Siddhesh Poyarekar
2016-01-28 17:55 ` Suzuki K. Poulose
2016-01-28 16:51 ` Adhemerval Zanella
2016-02-02 17:31 ` Szabolcs Nagy
2016-02-02 18:12 ` Adhemerval Zanella
2016-02-02 18:25 ` Szabolcs Nagy
2016-02-02 18:28 ` Adhemerval Zanella
2016-02-26 15:37 ` Catalin Marinas
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=56A79D17.2000009@arm.com \
--to=suzuki.poulose@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).