Skip to content
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.

Sign up for GitHub

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

Simplify FMV version selection rules #370

Merged
merged 2 commits into from
Jan 8, 2025
Merged

Simplify FMV version selection rules #370

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4d89c7f
Simplify FMV version selection rules
andrewcarlotti Dec 2, 2024
458e9f0
Merge branch 'main' into lex-priority
labrinea Jan 8, 2025
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
14 changes: 6 additions & 8 deletions main/acle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -423,6 +423,7 @@ Armv8.4-A [[ARMARMv84]](#ARMARMv84). Support is added for the Dot Product intrin
* Removed Function Multi Versioning features ebf16, memtag3, and rpres.
* Removed Function Multi Versioning feature dgh.
* Document Function Multi Versioning feature dependencies.
* Simplified Function Multi Versioning version selection rules.
* Fixed range of operand `o0` (too small) in AArch64 system register designations.
* Fixed SVE2.1 quadword gather load/scatter store intrinsics.
* Removed unnecessary Zd argument from `svcvtnb_mf8[_f32_x2]_fpm`.
Expand Down Expand Up @@ -2909,14 +2910,11 @@ the selection algorithm is platform dependent, where with platform means
CPU/Vendor/OS as in the target triplet.
2. The selection is permanent for the
lifetime of the process.
3. Only those versions could be considered where all
dependent features are available.

Rules of version selection are in order:

4. Select the most specific version else
5. select the version with the highest priority else
6. `"default"` is selected if no other versions are suitable.
3. Among any two versions, the higher priority version is determined by
identifying the highest priority feature that is specified in exactly one of
the versions, and selecting that version.
labrinea marked this conversation as resolved.
Show resolved Hide resolved
4. The selection algorithm must select the highest priority versions whose
labrinea marked this conversation as resolved.
Show resolved Hide resolved
dependent features are all available.

## Weak linkage

Expand Down
Loading