aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorSteven Wu <stevenwu@apple.com>2025-10-20 13:16:09 -0700
committerGitHub <noreply@github.com>2025-10-20 13:16:09 -0700
commitbe9c083cf7ec7dc9b6e93f29981d7b7e71273241 (patch)
treeb16938e64235795261487fe89b2bf03ab2128b9c /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent13498bc1d16005774a62b3dd04f1d2e5dd887674 (diff)
downloadllvm-be9c083cf7ec7dc9b6e93f29981d7b7e71273241.zip
llvm-be9c083cf7ec7dc9b6e93f29981d7b7e71273241.tar.gz
llvm-be9c083cf7ec7dc9b6e93f29981d7b7e71273241.tar.bz2
[CAS] Add OnDiskGraphDB and OnDiskKeyValueDB (#114102)
Add OnDiskGraphDB and OnDiskKeyValueDB that can be used to implement ObjectStore and ActionCache respectively. Those are on-disk persistent storage that build upon OnDiskTrieHashMap and implements key functions that are required by LLVMCAS interfaces. This abstraction layer defines how the objects are hashed and stored on disk. OnDiskKeyValueDB is a basic OnDiskTrieHashMap while OnDiskGraphDB also defines: * How objects of various size are store on disk and are referenced by the trie nodes. * How to store the references from one stored object to another object that is referenced. In addition to basic APIs for ObjectStore and ActionCache, other advances database configuration features can be implemented in this layer without exposing to the users of the LLVMCAS interface. For example, OnDiskGraphDB has a faulty in function to fetch data from an upstream OnDiskGraphDB if the data is missing.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions