-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
__has_builtin(__reference_binds_to_temporary) became false in Clang 19 #111477
Comments
@llvm/issue-subscribers-clang-frontend Author: None (timsong-cpp)
Likewise for `__has_builtin(__reference_constructs_from_temporary)`.
Is that intentional? What's the replacement if I want to detect whether the compiler supports them? |
`__has_builtin` was relying on reversible identifiers and string matching to recognize builtin-type traits, leading to some newer type traits not being recognized. Fixes llvm#111477
`__has_builtin` was relying on reversible identifiers and string matching to recognize builtin-type traits, leading to some newer type traits not being recognized. Fixes llvm#111477
@cor3ntin Can a fix for the two intrinsics named in the issue be backported to clang 19? This is a regression from clang 18 - and for |
This seems reasonable |
/cherry-pick 75611ca |
Failed to cherry-pick: 75611ca https://github.com/llvm/llvm-project/actions/runs/11249798451 Please manually backport the fix and push it to your github fork. Once this is done, please create a pull request |
`__has_builtin` was relying on reversible identifiers and string matching to recognize builtin-type traits, leading to some newer type traits not being recognized. Fixes llvm#111477
`__has_builtin` was relying on reversible identifiers and string matching to recognize builtin-type traits, leading to some newer type traits not being recognized. Fixes llvm#111477
Likewise for
__has_builtin(__reference_constructs_from_temporary)
.Is that intentional? What's the replacement if I want to detect whether the compiler supports them?
The text was updated successfully, but these errors were encountered: