diff options
| author | Sirraide <aeternalmail@gmail.com> | 2024-05-22 17:58:48 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-22 17:58:48 +0200 |
| commit | c44fa3e8a9a44c2e9a575768a3c185354b9f6c17 (patch) | |
| tree | 662fbb24054c0dff94a69494ad29d44ce7e79099 /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 4fbc95d1360147e9c4aceeadd1bda17d68364b85 (diff) | |
| download | llvm-c44fa3e8a9a44c2e9a575768a3c185354b9f6c17.zip llvm-c44fa3e8a9a44c2e9a575768a3c185354b9f6c17.tar.gz llvm-c44fa3e8a9a44c2e9a575768a3c185354b9f6c17.tar.bz2 | |
[Clang] Refactor `__attribute__((assume))` (#84934)
This is a followup to #81014 and #84582: Before this patch, Clang
would accept `__attribute__((assume))` and `[[clang::assume]]` as
nonstandard spellings for the `[[omp::assume]]` attribute; this
resulted in a potentially very confusing name clash with C++23’s
`[[assume]]` attribute (and GCC’s `assume` attribute with the same
semantics).
This pr replaces every usage of `__attribute__((assume))` with
`[[omp::assume]]` and makes `__attribute__((assume))` and
`[[clang::assume]]` alternative spellings for C++23’s `[[assume]]`;
this shouldn’t cause any problems due to differences in appertainment
and because almost no-one was using this variant spelling to begin
with (a use in libclc has already been changed to use a different
attribute).
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions
