Searched refs:deletions (Results 1 – 14 of 14) sorted by relevance
81 CK_HT_TYPE deletions; member168 map->deletions = 0; in ck_ht_map_create()451 CK_HT_TYPE_STORE(&map->deletions, map->deletions + 1); in ck_ht_gc()461 CK_HT_TYPE_STORE(&map->deletions, map->deletions + 1); in ck_ht_gc()536 d = CK_HT_TYPE_LOAD(&map->deletions); in ck_ht_map_probe_rd()575 d_prime = CK_HT_TYPE_LOAD(&map->deletions); in ck_ht_map_probe_rd()791 d = CK_HT_TYPE_LOAD(&map->deletions); in ck_ht_get_spmc()801 d_prime = CK_HT_TYPE_LOAD(&map->deletions); in ck_ht_get_spmc()882 CK_HT_TYPE_STORE(&map->deletions, map->deletions + 1); in ck_ht_set_spmc()895 CK_HT_TYPE_STORE(&map->deletions, map->deletions + 1); in ck_ht_set_spmc()[all …]
12 3 files changed, 59 insertions(+), 2 deletions(-)
789 std::vector<std::string> deletions; member in dtc::fdt::device_tree
1677 deletions.push_back(std::move(ref)); in parse_file()2098 for (auto &ref : deletions) in parse_dts()
29 The hash chains are singly linked. There are no deletions from the
33 substantive changes or deletions from the original are clearly814 deletions from the hash chains; the algorithm simply discards matches
35 substantive changes or deletions from the original are clearly
33 substantive changes or deletions from the original are clearly
13 and that any substantive changes or deletions from the original
358 To ignore insertions and deletions of lines that match a747 @var{from-file} are omitted. If all of the changes are deletions, the
9001 …g rescattered. Moreover, it can be used to eliminate previously flagged deletions from any hash-co…9009 …keywords = "deletions; dynamic storage; hash code; programming; reallocation; scatter storage;…16895 … coding; compression of numbers; data handling; decimal data; decoding; deletions; Huffman codes; …22573 …eight-balanced trees can be done in O(log**2N) steps. It is proved that deletions can also be perf…22580 …keywords = "deletions; insertions; one sided height balanced trees; programming theory; trees …
11233 of deletions cannot do this from netevent. This means when using
8571 cursor movement, and single-character deletions work properly.
9569 (local) cache must be locked during all cache object deletions. Andrew