diff options
| author | Craig Topper <craig.topper@intel.com> | 2019-03-26 05:31:32 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2019-03-26 05:31:32 +0000 |
| commit | 4dcabf8ddfa2a1f93e15700fd463b79baa6afd9b (patch) | |
| tree | c3c5057734481057399bbbcfbcc9c6a21a3bac64 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp | |
| parent | 10576fea828bb17b3ee6a0f8ae39dbdf409535eb (diff) | |
[X86] In matchBitExtract, place all of the new nodes before Node's position in the DAG for the topological sort.
We were using OrigNBits, but that put all the nodes before the node we used to start the control computation. This caused some node earlier than the sequence we inserted to be selected before the sequence we created. We want our new sequence to be selected first since it depends on OrigNBits.
I don't have a test case. Found by reviewing the code.
llvm-svn: 356979
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions