diff options
| author | Philip Reames <listmail@philipreames.com> | 2019-09-03 21:56:17 +0000 |
|---|---|---|
| committer | Philip Reames <listmail@philipreames.com> | 2019-09-03 21:56:17 +0000 |
| commit | 30dc2da8273fa9cb2d62b0b0536389f40335fb62 (patch) | |
| tree | 764055daa67f5ad3d1ede308a94f3f5f8a93b5d9 /lldb/packages/Python/lldbsuite/test/lang/cpp/namespace/TestNamespace.py | |
| parent | 2a2c25ba480016f8ad8fa407af7627d84547637d (diff) | |
| download | bcm5719-llvm-30dc2da8273fa9cb2d62b0b0536389f40335fb62.tar.gz bcm5719-llvm-30dc2da8273fa9cb2d62b0b0536389f40335fb62.zip | |
[GVN] Remove a todo introduced w/rL370791
When I dug into this, it turns out to be *much* more involved than I'd realized and doesn't actually simplify anything.
The general purpose of the leader table is that we want to find the most-dominating definition quickly. The problem for equivalance folding is slightly different; we want to find the most dominating *value* whose definition block dominates our use quickly.
To make this change, we'd end up having to restructure the leader table (either the sorting thereof, or maybe even introducing multiple leader tables per value) and that complexity is just not worth it.
llvm-svn: 370824
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/namespace/TestNamespace.py')
0 files changed, 0 insertions, 0 deletions
