Skip to content

Commit

Permalink
[FMV] Use lexicographic order of feature names when mangling.
Browse files Browse the repository at this point in the history
This decouples feature priorities from name mangling. Doing so will
prevent ABI breakages in case we change the feature priorities.
  • Loading branch information
labrinea committed Mar 1, 2024
1 parent 59c2d69 commit f9294c2
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions main/acle.md
Original file line number Diff line number Diff line change
Expand Up @@ -2524,16 +2524,16 @@ the [[cxxabi]](#cxxabi), and it is defined as follows:
<vendor specific suffix> := `_` followed by token obtained from the tables below and prefixed with `M`
```

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

For example:
``` c
__attribute__((target_clones("crc32", "aes+sha1")))
int foo(){..}
```
will produce these mangled names for C language: `foo`, `foo._Mcrc32`,
`foo._Msha1Maes`.
`foo._MaesMsha1`.


### Mapping
Expand Down

0 comments on commit f9294c2

Please sign in to comment.