Add intrinsics for the FEAT_SVE2p2/FEAT_SME2p2 features introduced by the 2024 dpISA #412

amilendra · 2025-09-15T16:00:39Z

name: Pull request
about: Technical issues, document format problems, bugs in scripts or feature proposal.

Thank you for submitting a pull request!

If this PR is about a bugfix:

Please use the bugfix label and make sure to go through the checklist below.

If this PR is about a proposal:

We are looking forward to evaluate your proposal, and if possible to
make it part of the Arm C Language Extension (ACLE) specifications.

We would like to encourage you reading through the contribution
guidelines, in particular the section on submitting
a proposal.

Please use the proposal label.

As for any pull request, please make sure to go through the below
checklist.

Checklist: (mark with X those which apply)

If an issue reporting the bug exists, I have mentioned it in the
PR (do not bother creating the issue if all you want to do is
fixing the bug yourself).
I have added/updated the SPDX-FileCopyrightText lines on top
of 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 use
commas to separate gaps, as in 2018-2020, 2022).
I have updated the Copyright section of the sources of the
specification 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.
I have run the CI scripts (if applicable, as they might be
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.
I have added an item that describes the changes I have
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.
When modifying content and/or its rendering, I have checked the
correctness of the result in the PDF output (please refer to the
instructions on how to build the PDFs
locally).
The variable draftversion is set to true in the YAML header
of the sources of the specifications I have modified.
Please DO NOT add my GitHub profile to the list of contributors
in the README page of the project.

main/acle.md

AlfieRichardsArm · 2025-09-18T10:14:40Z

~~This seems to be missing~~
~~- the zeroing forms of all the unary instructions added in S(M|V)E2p2? Such as NOT (zeroing) and REVB (zeroing) and lots more.~~
~~- FRECPX~~
~~- FSQRT~~

~~Will they be added separately?~~

Corrected offline that these intrinsics are all already present, and will just be simplified by the new instructions.

Lukacma · 2025-09-23T14:45:38Z

main/acle.md

+ [`<arm_sve.h>`](#arm_sve.h) or [`<arm_sme.h>`](#arm_sme.h)
+when `__ARM_FEATURE_SVE2p2` or `__ARM_FEATURE_SME2p2` is defined, respectively.
+
+These intrinsics can only be called from non-streaming code if


So this is not correct. These instruction can be called in non-streaming mode if we have sme2p2 and sve as well.

For FIRSTP and LASTP you can also run them in streaming mode if you have sve2p2 and sme.

I've updated the conditions. Please can you have another look?

main/acle.md

Lukacma

LGTM

main/acle.md

CarolineConcatto · 2025-10-06T16:22:25Z

main/acle.md

+`__ARM_FEATURE_SME2p2` feature macro is defined.
+
+They can be called from non-streaming code if the `__ARM_FEATURE_SVE2p2` feature
+macro is defined or both the `__ARM_FEATURE_SVE` and `__ARM_FEATURE_SME2p2`


I am not sure this is correct:
__ARM_FEATURE_SVE and __ARM_FEATURE_SME2p2
should it be:
__ARM_FEATURE_SME and __ARM_FEATURE_SME2p2
Why are you writing that it needs SVE, have you seeing this in the pseudo code from the instruction?

Yes. Actually that is something I understood from the pseudocode.

For example the psuedocode of COMPACT checks for SVE

It was not immediately obvious to me either, and was pointed out by @Lukacma

The size that is now available also in sme2p2 and sve is Word and doubleword.
You are adding new ones that are only available for sve2p2 or sme2p2

Removed those conditions because it is simply repeating information already available in the ISA docs.

CarolineConcatto · 2025-10-06T16:25:02Z

main/acle.md

+
+Scalar index of first/last true predicate element (predicated).
+
+These intrinsics can be called from streaming mode if either of the feature


I believe this is incorrect. Can you remove these sentences?
They need sve2p2 or sme2p2, there is nothing saying about sve or sme.

Similar to COMPACT, this is also something I understood from the CheckSVEEnabled pseudocode used by FIRSTP

That is when the instructions is defined:
if !IsFeatureImplemented(FEAT_SVE2p2) && !IsFeatureImplemented(FEAT_SME2p2) then
CheckSVEEnabled is how it will run, in streaming mode or sve.

Removed those conditions because it is simply repeating information already available in the ISA docs.

main/acle.md

CarolineConcatto · 2025-10-06T16:26:59Z

main/acle.md

+
+Copy active vector elements to/from lower-numbered elements.
+
+These intrinsics can be called from streaming code only if the


I believe this sentence are applied to all sve2p2 and sme2p2 instruction you can move it up. After line 13601

Removed those conditions because it is simply repeating information already available in the ISA docs.

Lukacma · 2025-10-14T12:16:31Z

main/acle.md

+
+``` c
+  // Variants are also available for:
+  // [_single_f32_x2]


I think we should split this into x2 and x4 variants. I think this might confuse users as to what type to use for arguments.

I've split them up. Does this look okay?

main/acle.md

These instructions are available under features FEAT_SVE2p2 or FEAT_SME2p2. COMPACT: Copy Active vector elements to lower-numbered elements (Byte/Halfword variants) EXPAND: Copy lower-numbered vector elements to Active elements (Byte/Halfword/Word/Doubleword variants) FIRSTP: Scalar index of first true predicate element (predicated) (Byte/Halfword/Word/Doubleword variants) LASTP: Scalar index of last true predicate element (predicated) (Byte/Halfword/Word/Doubleword variants) FMUL (multiple and single vector): Multi-vector floating-point multiply by vector FMUL (multiple vectors): Multi-vector floating-point multiply

…ing code

1. Change firstp/lastp parameter names to match the register names: op -> pn 2. split the x2 and x4 variants of the FMUL intrinsics

Lukacma · 2025-11-14T12:05:21Z

main/acle.md

+extended in the future.
+
+The intrinsics in this section are defined by the header file
+[`<arm_sme.h>`](#arm_sme.h) when `__ARM_FEATURE_SME2p2` is defined.


Since these instructions do not operate on ZA array, I think they should be in arm_sve.h.

CarolineConcatto · 2025-11-19T10:49:32Z

We need to add these new instructions also:
FRINT32X
FRINT32Z
FRINT64X
FRINT64Z
They are sve2p2 as well

amilendra force-pushed the 2025-acle-sve-sme2p2 branch from b421a82 to 2dd7a0d Compare September 16, 2025 12:41

AlfieRichardsArm reviewed Sep 17, 2025

View reviewed changes

main/acle.md Outdated Show resolved Hide resolved

AlfieRichardsArm reviewed Sep 17, 2025

View reviewed changes

main/acle.md Outdated Show resolved Hide resolved

AlfieRichardsArm reviewed Sep 17, 2025

View reviewed changes

main/acle.md Outdated Show resolved Hide resolved

amilendra force-pushed the 2025-acle-sve-sme2p2 branch from 2dd7a0d to 137ff03 Compare September 18, 2025 14:04

Lukacma reviewed Sep 23, 2025

View reviewed changes

mgabka reviewed Sep 24, 2025

View reviewed changes

main/acle.md Outdated Show resolved Hide resolved

amilendra force-pushed the 2025-acle-sve-sme2p2 branch from 137ff03 to 7de9269 Compare October 1, 2025 15:02

amilendra mentioned this pull request Oct 2, 2025

Add support for the Brain 16-bit floating-point vector multiplication (FEAT_SVE_BFSCALE) intrinsics #410

Open

8 tasks

amilendra changed the title ~~Add support for COMPACT/EXPAND and FIRSTP/LASTP intrinsics~~ Add intrinsics for the FEAT_SVE2p2/FEAT_SME2p2 features introduced by the 2024 dpISA Oct 2, 2025

Lukacma approved these changes Oct 3, 2025

View reviewed changes

CarolineConcatto reviewed Oct 6, 2025

View reviewed changes

amilendra force-pushed the 2025-acle-sve-sme2p2 branch from ff8fbf9 to 777686d Compare October 7, 2025 15:48

Lukacma suggested changes Oct 14, 2025

View reviewed changes

This was referenced Oct 14, 2025

[AArch64] Add intrinsics support for multi-vector FMUL llvm/llvm-project#163397

Open

[AArch64] Add intrinsics support for SVE2p2 instructions llvm/llvm-project#163575

Open

kmclaughlin-arm reviewed Oct 23, 2025

View reviewed changes

main/acle.md Outdated Show resolved Hide resolved

amilendra added 4 commits October 24, 2025 11:45

Add SME2.2/SVE2.2 support status (Alpha) to the content

78c7dd0

SME/SVE2.2 Remove conditions for being called by streaming/non-stream…

09763cc

…ing code

Address review comments

29f8554

1. Change firstp/lastp parameter names to match the register names: op -> pn 2. split the x2 and x4 variants of the FMUL intrinsics

amilendra force-pushed the 2025-acle-sve-sme2p2 branch from 5f3e66f to 29f8554 Compare October 24, 2025 12:42

Lukacma reviewed Nov 14, 2025

View reviewed changes

Lukacma added 2 commits November 19, 2025 12:04

add frint intrinsics

fd2e712

remove empty lines

52d1f8d


		Scalar index of first/last true predicate element (predicated).

		These intrinsics can be called from streaming mode if either of the feature


		Copy active vector elements to/from lower-numbered elements.

		These intrinsics can be called from streaming code only if the

Add intrinsics for the FEAT_SVE2p2/FEAT_SME2p2 features introduced by the 2024 dpISA #412

Are you sure you want to change the base?

Add intrinsics for the FEAT_SVE2p2/FEAT_SME2p2 features introduced by the 2024 dpISA #412

Uh oh!

Conversation

amilendra commented Sep 15, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

AlfieRichardsArm commented Sep 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Lukacma left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Lukacma Oct 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CarolineConcatto commented Nov 19, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

AlfieRichardsArm commented Sep 18, 2025 •

edited

Loading

Lukacma Oct 14, 2025 •

edited

Loading