History log of /llvm-project/llvm/lib/Support/TrieRawHashMap.cpp (Results 1 – 3 of 3)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6, llvmorg-19.1.5, llvmorg-19.1.4
# 03948882 30-Oct-2024 Simon Pilgrim <llvm-dev@redking.me.uk>

Fix MSVC "32-bit shift implicitly converted to 64 bits" warning. NFC

NumBits should be less than 20 so using an unsigned instead of size_t should be OK


# ba8d9ce8 29-Oct-2024 Steven Wu <stevenwu@apple.com>

[ADT] Fix unused variable from #69528 (#114114)

Remove unused variable to fix build failures from bot.


# b510cdb8 29-Oct-2024 Steven Wu <stevenwu@apple.com>

[ADT] Add TrieRawHashMap (#69528)

Implement TrieRawHashMap can be used to store object with its associated
hash. User needs to supply a strong hashing function to guarantee the
uniqueness of the h

[ADT] Add TrieRawHashMap (#69528)

Implement TrieRawHashMap can be used to store object with its associated
hash. User needs to supply a strong hashing function to guarantee the
uniqueness of the hash of the objects to be inserted. A hash collision
is not supported and will lead to error or failed to insert.

TrieRawHashMap is thread-safe and lock-free and can be used as
foundation data structure to implement a content addressible storage.
TrieRawHashMap owns the data stored in it and is designed to be:
* Fast to lookup.
* Fast to "insert" if the data has already been inserted.
* Can be used without lock and doesn't require any knowledge of the
participating threads or extra coordination between threads.

It is not currently designed to be used to insert unique new data with
high contention, due to the limitation on the memory allocator.

show more ...