Add alpha support for 9.7 data processing intrinsics #428
Conversation
This change adds intrinsics for the following architectural features: - FEAT_F16F32DOT - FEAT_F16F32MM - FEAT_F16MM - FEAT_SVE_B16MM - FEAT_SVE2p3 - FEAT_SME2p3
| Add pairwise within quadword vector segments. | ||
|
|
||
| ``` c | ||
| // Variants are also available for _s16, _s32 and _s64 |
There was a problem hiding this comment.
We should also have unsigned variants here.
| Add subtract pairwise. | ||
|
|
||
| ``` c | ||
| // Variants are also available for _s16, _s32 and _s64 |
There was a problem hiding this comment.
We should also have unsigned variants here?
|
|
||
| #### SDOT, UDOT (vectors) | ||
|
|
||
| Integer dot-product (2-way, vectors). |
There was a problem hiding this comment.
"2-way" vs "two-way" are used inconsistently, pick one? Personal preference for the latter, but fine with either.
| svfloat16_t svcvtb_f16[_s8](svint8_t zn); | ||
| ``` | ||
|
|
||
| #### SDOT, UDOT (vectors) |
There was a problem hiding this comment.
There should already be a section for the _s32_s16 etc variant of this added with FEAT_SVE2p1 somewhere else in this doc, should this be merged into that?
|
|
||
| ``` c | ||
| // Variants are also available for | ||
| // _u16[_u32_x2] |
There was a problem hiding this comment.
Rework this so that signed/unsigned are on their own lines instead of grouping by 8/16, then we can fix the alignment here?
| Subtract pairwise. | ||
|
|
||
| ``` c | ||
| // Variants are also available for _s16, _s32 and _s64 |
There was a problem hiding this comment.
This should have unsigned variants?
2 participants
name: Add alpha support for 9.7 data processing intrinsics
about: feature proposal.
This change adds intrinsics for the following architectural features:
Checklist: (mark with
Xthose which apply)PR (do not bother creating the issue if all you want to do is
fixing the bug yourself).
SPDX-FileCopyrightTextlines on topof any file I have edited. Format is
SPDX-FileCopyrightText: Copyright {year} {entity or name} <{contact informations}>(Please update existing copyright lines if applicable. You can
specify year ranges with hyphen , as in
2017-2019, and usecommas to separate gaps, as in
2018-2020, 2022).Copyrightsection of the sources of thespecification I have edited (this will show up in the text
rendered in the PDF and other output format supported). The
format is the same described in the previous item.
tricky to set up on non-*nix machines). The sequence can be
found in the contribution
guidelines. Don't
worry if you cannot run these scripts on your machine, your
patch will be automatically checked in the Actions of the pull
request.
introduced in this PR in the section Changes for next
release of the section Change Control/Document history
of the document. Create Changes for next release if it does
not exist. Notice that changes that are not modifying the
content and rendering of the specifications (both HTML and PDF)
do not need to be listed.
correctness of the result in the PDF output (please refer to the
instructions on how to build the PDFs
locally).
draftversionis set totruein the YAML headerof the sources of the specifications I have modified.
in the README page of the project.