diff options
| author | JF Bastien <jfb@google.com> | 2016-04-12 18:06:55 +0000 |
|---|---|---|
| committer | JF Bastien <jfb@google.com> | 2016-04-12 18:06:55 +0000 |
| commit | 5502e91c8b6a3f069f4c5770b7aaef9c8b0f002a (patch) | |
| tree | 5e1ab5869a21d131c4dca4fe46098bf936154eed /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp | |
| parent | 92d1f0cb6d4f66a285e3e85bfc2d55fb96b16ae9 (diff) | |
| download | bcm5719-llvm-5502e91c8b6a3f069f4c5770b7aaef9c8b0f002a.tar.gz bcm5719-llvm-5502e91c8b6a3f069f4c5770b7aaef9c8b0f002a.zip | |
Check alloca's special state
Following up to a similar fix in MergeFunctions: r266022. This patch keeps both in sync, it would be nice to not have to do this. It doesn't look like there's an easy way to test this code directly at the moment: AFAICT all currect uses of isSameOperationAs are looking at instructions deep inside a function. IndVarSimplify/pr24952.ll and InstMerge/st_sink_* look at alloca inadvertently but are brittle tests.
llvm-svn: 266099
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
