diff options
author | A. Jiang <de34@live.cn> | 2025-06-03 10:34:45 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-06-03 10:34:45 +0800 |
commit | 437ad06f762ab07d89badecdd20627db200b98d3 (patch) | |
tree | 089a4cb23a979d8e1cea55facf7396a4e5d79fd6 /llvm/lib/CodeGen/MachineScheduler.cpp | |
parent | 6f64a600649a95141526043b170aa4244d54c94b (diff) | |
download | llvm-437ad06f762ab07d89badecdd20627db200b98d3.zip llvm-437ad06f762ab07d89badecdd20627db200b98d3.tar.gz llvm-437ad06f762ab07d89badecdd20627db200b98d3.tar.bz2 |
[libc++] Use `__reference_constructs_from_temporary` if eligible (#141916)
Currently, libc++'s `<tuple>` is using the deprecated
`__reference_binds_to_temporary` intrinsic. This PR starts to use
`__reference_constructs_from_temporary` if possible.
It seems that `__reference_constructs_from_temporary` should be used via
an internal type traits provided in
`<__type_traits/reference_constructs_from_temporary.h>`. But given the
old intrinsic was directly used, this PR doesn't switch to the current
convention yet.
P2255R2 is related. Although the paper indicated that constructors of
`tuple` should be deleted in such a case.
---------
Co-authored-by: Nikolas Klauser <nikolasklauser@berlin.de>
Diffstat (limited to 'llvm/lib/CodeGen/MachineScheduler.cpp')
0 files changed, 0 insertions, 0 deletions