Skip to content

Make intrinsics available in function scope #214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions main/acle.md
Original file line number Diff line number Diff line change
Expand Up @@ -316,6 +316,10 @@ Armv8.4-A [[ARMARMv84]](#ARMARMv84). Support is added for the Dot Product intrin
* added `FEAT_LS64*`.
* Added feature detection macro `__ARM_FEATURE_RCPC` for RCpc (Release Consistent processor consistent) model at [RCpc](#rcpc).

#### Changes for next release

* Add intrinsics availability to function scope.

### References

This document refers to the following documents.
Expand Down Expand Up @@ -700,6 +704,15 @@ ACLE standardizes intrinsics to access various features of the
Arm ® architecture. It also standardizes a set of [header
files](#header-files) that provide access to these intrinsics.

Availability of a given intrinsics is indicated by the corresponding
`_ARM_FEATURE_` macro, as detailed in the [Feature test
macros](#feature-test-macros) section. A given architecture feature could
be enabled in function scope, for example with the `target` or
[`target_version`](#function-multi-versioning) attributes. If an
implementation supports such then the related intrinsics of the enabled
architecture feature must be available in that scope via the standard
header files.

Whether intrinsics are macros, functions or built-in operators is
unspecified. For example:

Expand Down