aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/lldbdwarf.py
diff options
context:
space:
mode:
authorSam McCall <sam.mccall@gmail.com>2023-06-22 21:54:52 +0200
committerSam McCall <sam.mccall@gmail.com>2023-06-26 21:16:25 +0200
commitd85c233e4b05497a6d8c6e3f2a5fd63d9eeb200d (patch)
tree1d15f29816f0478e3d56c6d1d30baebf0fdcab01 /lldb/packages/Python/lldbsuite/test/lldbdwarf.py
parentc32c0e14d6944d6a0e36191d7b5bf6943f96092e (diff)
downloadllvm-d85c233e4b05497a6d8c6e3f2a5fd63d9eeb200d.zip
llvm-d85c233e4b05497a6d8c6e3f2a5fd63d9eeb200d.tar.gz
llvm-d85c233e4b05497a6d8c6e3f2a5fd63d9eeb200d.tar.bz2
[dataflow] Make SAT solver deterministic
The SAT solver imported its constraints by iterating over an unordered DenseSet. The path taken, and ultimately the runtime, the specific solution found, and whether it would time out or complete could depend on the iteration order. Instead, have the caller specify an ordered collection of constraints. If this is built in a deterministic way, the system can have deterministic behavior. (The main alternative is to sort the constraints by value, but this option is simpler today). A lot of nondeterminism still appears to be remain in the framework, so today the solver's inputs themselves are not deterministic yet. Differential Revision: https://reviews.llvm.org/D153584
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbdwarf.py')
0 files changed, 0 insertions, 0 deletions