Home
last modified time | relevance | path

Searched refs:dangling (Results 1 – 25 of 92) sorted by relevance

1234

/llvm-project-15.0.7/libcxx/test/std/algorithms/
H A Dranges_robust_against_dangling.pass.cpp67 using std::ranges::dangling; in test_all()
120 dangling_both<mismatch_result<dangling, dangling>>(std::ranges::mismatch, in, in2); in test_all()
143 dangling_1st<binary_transform_result<dangling, int*, bool*>>( in test_all()
145 dangling_2nd<binary_transform_result<int*, dangling, bool*>>( in test_all()
147 dangling_both<binary_transform_result<dangling, dangling, bool*>>( in test_all()
159 dangling_both<swap_ranges_result<dangling, dangling>>(std::ranges::swap_ranges, in, in2); in test_all()
166 …dangling_both<partial_sort_copy_result<dangling, dangling>>(std::ranges::partial_sort_copy, in, in… in test_all()
169 dangling_both<merge_result<dangling, dangling, int*>>(std::ranges::merge, in, in2, out); in test_all()
173 …dangling_both<set_intersection_result<dangling, dangling, int*>>(std::ranges::set_intersection, in… in test_all()
178 dangling_both<set_symmetric_difference_result<dangling, dangling, int*>>( in test_all()
[all …]
/llvm-project-15.0.7/libcxx/test/std/ranges/range.utility/range.dangling/
H A Ddangling.pass.cpp19 static_assert(std::is_empty_v<std::ranges::dangling>);
22 static_assert(std::is_nothrow_constructible_v<std::ranges::dangling>);
23 static_assert(std::is_nothrow_constructible_v<std::ranges::dangling, S<0>>);
24 static_assert(std::is_nothrow_constructible_v<std::ranges::dangling, S<0>, S<1>>);
25 static_assert(std::is_nothrow_constructible_v<std::ranges::dangling, S<0>, S<1>, S<2>>);
28 [[maybe_unused]] auto a = std::ranges::dangling(); in test_dangling()
29 [[maybe_unused]] auto b = std::ranges::dangling(S<0>()); in test_dangling()
30 [[maybe_unused]] auto c = std::ranges::dangling(S<0>(), S<1>()); in test_dangling()
31 [[maybe_unused]] auto d = std::ranges::dangling(S<0>(), S<1>(), S<2>()); in test_dangling()
H A Dborrowed_iterator.compile.pass.cpp22 static_assert(std::same_as<std::ranges::borrowed_iterator_t<std::string>, std::ranges::dangling>);
23 static_assert(std::same_as<std::ranges::borrowed_iterator_t<std::string&&>, std::ranges::dangling>);
24 …c_assert(std::same_as<std::ranges::borrowed_iterator_t<std::vector<int> >, std::ranges::dangling>);
H A Dborrowed_subrange.compile.pass.cpp22 static_assert(std::same_as<std::ranges::borrowed_subrange_t<std::string>, std::ranges::dangling>);
23 static_assert(std::same_as<std::ranges::borrowed_subrange_t<std::string&&>, std::ranges::dangling>);
24 …c_assert(std::same_as<std::ranges::borrowed_subrange_t<std::vector<int> >, std::ranges::dangling>);
/llvm-project-15.0.7/libcxx/include/__ranges/
H A Ddangling.h27 struct dangling { struct
28 dangling() = default;
29 _LIBCPP_HIDE_FROM_ABI constexpr dangling(auto&&...) noexcept {} in dangling() argument
33 using borrowed_iterator_t = _If<borrowed_range<_Rp>, iterator_t<_Rp>, dangling>;
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Ddangling-handle.rst1 .. title:: clang-tidy - bugprone-dangling-handle
3 bugprone-dangling-handle
6 Detect dangling references in value handles like ``std::string_view``.
7 These dangling references can be a result of constructing handles from temporary
19 V.push_back(string()); // V[0] is dangling.
/llvm-project-15.0.7/clang/test/Analysis/
H A Dcxx-uninitialized-object-ptr-ref.cpp76 stack upon returning to the caller. This will be a dangling reference}}
94 stack upon returning to the caller. This will be a dangling reference}}
107 stack upon returning to the caller. This will be a dangling reference}}
355 upon returning to the caller. This will be a dangling reference}}
372 upon returning to the caller. This will be a dangling reference}}
389 upon returning to the caller. This will be a dangling reference}}
/llvm-project-15.0.7/llvm/test/DebugInfo/X86/
H A Ddbg-val-list-dangling.ll1 ;; At the moment we emit an undef as soon as we encounter "dangling" variadic
5 ;; FIXME: When dangling nodes for a variadic dbg_value are found, we should be
10 ;; Check that dangling debug info in the SelectionDAG build phase is handled
/llvm-project-15.0.7/llvm/test/Transforms/SampleProfile/
H A Dprofile-inference-rebalance.ll107 ; The test contains a triangle comprised of dangling blocks.
180 ; The test contains a dangling subgraph that contains an exit dangling block.
225 ; Another dangling subgraph (b42, b43, b44) containing a single dangling block.
H A Dpseudo-probe-dangle3.ll1 ; Test after FoldValueComparisonIntoPredecessors, one dangling probe is gone
/llvm-project-15.0.7/libcxx/include/
H A Dranges109 // [range.dangling], dangling iterator handling
110 struct dangling;
282 #include <__ranges/dangling.h>
/llvm-project-15.0.7/clang/test/SemaObjC/
H A Dproperty-assign-on-object-type.m7 …o1; // expected-warning {{'assign' property of object type may become a dangling reference; consid…
/llvm-project-15.0.7/llvm/test/Transforms/SimpleLoopUnswitch/
H A Ddead-blocks-uses-in-unreachablel-blocks.ll6 ; Make sure we don't crash due to a dangling use of %tmp2 in bb7.
/llvm-project-15.0.7/libcxx/test/std/algorithms/alg.modifying.operations/alg.transform/
H A Dranges.transform.pass.cpp480 std::same_as<std::ranges::in_out_result<std::ranges::dangling, int*>> auto ret = in test()
489 std::same_as<std::ranges::in_in_out_result<std::ranges::dangling, int*, int*>> auto ret = in test()
498 std::same_as<std::ranges::in_in_out_result<int*, std::ranges::dangling, int*>> auto ret = in test()
506 …std::same_as<std::ranges::in_in_out_result<std::ranges::dangling, std::ranges::dangling, int*>> au… in test()
/llvm-project-15.0.7/libcxx/test/std/algorithms/alg.modifying.operations/alg.swap/
H A Dranges.swap_ranges.pass.cpp150 using Expected = std::ranges::swap_ranges_result<int*, std::ranges::dangling>; in test_rval_range()
158 using Expected = std::ranges::swap_ranges_result<std::ranges::dangling, int*>; in test_rval_range()
/llvm-project-15.0.7/llvm/test/tools/llvm-profdata/
H A Dmerge-probe-profile.test2 # Check the dangling probe 3 ends up with 18446744073709551615 (INT64_MAX), i.e, not aggregated.
/llvm-project-15.0.7/llvm/test/CodeGen/AArch64/
H A Darm64-2012-01-11-ComparisonDAGCrash.ll4 ; during operation legalization, which resulted in dangling pointers,
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/readability/
H A Dmisleading-indentation.rst11 The way to avoid dangling else is to always check that an ``else`` belongs
/llvm-project-15.0.7/lldb/test/Shell/SymbolFile/DWARF/x86/
H A Ddebug-types-missing-signature.test1 Create a dangling DW_AT_signature reference by stripping the debug_types
/llvm-project-15.0.7/libcxx/
H A D.clang-tidy3 bugprone-dangling-handle,
/llvm-project-15.0.7/llvm/test/DebugInfo/ARM/
H A Dselectiondag-deadcode.ll16 ; of the vreg holding %agg.result) the dbg_value becomes dangling
/llvm-project-15.0.7/mlir/
H A D.clang-tidy7 bugprone-dangling-handle,
/llvm-project-15.0.7/llvm/test/CodeGen/Generic/
H A Ddag-combine-ossfuzz-crash.ll4 ; llc built with address sanitizer crashes because of a dangling node pointer
/llvm-project-15.0.7/llvm/test/Transforms/LoopUnroll/
H A Dinvalidate_right_loop.ll6 ; Make sure that this test doesn't crash because of dangling pointer in SCEV.
/llvm-project-15.0.7/llvm/test/TableGen/
H A Difstmt.td58 // Test resolution of the dangling-else ambiguity.

1234