From: Loic Dachary <loic@dachary.org>
To: Janne Grunau <j@jannau.net>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: NEON / SIMD
Date: Mon, 13 Oct 2014 19:36:17 -0700 [thread overview]
Message-ID: <543C8C21.6040806@dachary.org> (raw)
In-Reply-To: <20141013100651.GI2532@jannau.net>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On 13/10/2014 03:06, Janne Grunau wrote:
> Hi,
>
> On 2014-10-11 23:13:26 +0200, Loic Dachary wrote:
>>
>> I'd like to learn more about SIMD and NEON. What documents / web site
>> would you recommend to begin ? There are
>>
>> http://projectne10.github.io/Ne10/
>> http://www.arm.com/products/processors/technologies/neon.php
>>
>> Are you using formal specifications / documentations ? Any hint would
>> be most appreciated :-)
>
> I'm almost exclusively using ARM's Architecture Reference Manuals
> (available only after registration in ARM's inforcenter):
>
> ARMv7-A:
> http://infocenter.arm.com/help/topic/com.arm.doc.ddi0406c/index.html
>
> ARMv8-A:
> http://infocenter.arm.com/help/topic/com.arm.doc.ddi0487a.c/index.html
>
>
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0489h/DUI0489H_arm_assembler_reference.pdf
> Seems to be available without registration and has similar descriptions
> of neon and vfp instructions like the ARMv7-A ARM.
>
> I don't know any more approachable source off-hand.
Thanks for the tip :-) I'm registered and can see the documents now !
Cheers
>
> Janne
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-10-14 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 21:13 NEON / SIMD Loic Dachary
2014-10-13 10:06 ` Janne Grunau
2014-10-14 2:36 ` Loic Dachary [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=543C8C21.6040806@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=j@jannau.net \
/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