Skip to content

Commit 6e44d46

Browse files
authored
[FMV] Use lexicographic order of feature names when mangling. (#303)
This decouples feature priorities from name mangling. Doing so will prevent ABI breakages in case we change the feature priorities.
1 parent 59c2d69 commit 6e44d46

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

main/acle.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2524,16 +2524,16 @@ the [[cxxabi]](#cxxabi), and it is defined as follows:
25242524
<vendor specific suffix> := `_` followed by token obtained from the tables below and prefixed with `M`
25252525
```
25262526

2527-
If multiple features are requested then those shall be appended in increasing
2528-
priority order and prefixed with `M`.
2527+
If multiple features are requested then those shall be appended in lexicographic
2528+
order and prefixed with `M`.
25292529

25302530
For example:
25312531
``` c
25322532
__attribute__((target_clones("crc32", "aes+sha1")))
25332533
int foo(){..}
25342534
```
25352535
will produce these mangled names for C language: `foo`, `foo._Mcrc32`,
2536-
`foo._Msha1Maes`.
2536+
`foo._MaesMsha1`.
25372537

25382538

25392539
### Mapping

0 commit comments

Comments
 (0)