aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp
diff options
context:
space:
mode:
authorArnaud A. de Grandmaison <arnaud.degrandmaison@arm.com>2015-02-11 08:25:36 +0000
committerArnaud A. de Grandmaison <arnaud.degrandmaison@arm.com>2015-02-11 08:25:36 +0000
commitde79026d5e781842b0f97e00b2fbc8ef081ebeee (patch)
tree648fd50e69b6eb5dd41f8e08971b2c8cfcc78fe3 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp
parent9fd8cdc00917ee50db665292a47c1262d98ae00e (diff)
downloadllvm-de79026d5e781842b0f97e00b2fbc8ef081ebeee.zip
llvm-de79026d5e781842b0f97e00b2fbc8ef081ebeee.tar.gz
llvm-de79026d5e781842b0f97e00b2fbc8ef081ebeee.tar.bz2
[PBQP] Cautiously update edge costs in the solver
The NodeMetadata are maintained in an incremental way. When an edge between 2 nodes has its cost updated, in the course of graph reduction for example, the NodeMetadata need first to have the old edge cost removed, then the new edge cost added. Only once the NodeMetadata have been fully updated, it becomes safe to consider promoting the nodes to the ConservativelyAllocatable or OptimallyReducible sets. Previously, this promotion was occuring right after the removing the old cost, and this was breaking the assumption that a ConservativelyAllocatable should not be spilled. This patch also adds asserts to: - enforces the invariant that a node's reduction can not be downgraded, - only not provably allocatable or optimally reducible nodes can be spilled. llvm-svn: 228816
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp')
0 files changed, 0 insertions, 0 deletions