diff options
| author | Saleem Abdulrasool <compnerd@compnerd.org> | 2016-03-25 19:48:06 +0000 |
|---|---|---|
| committer | Saleem Abdulrasool <compnerd@compnerd.org> | 2016-03-25 19:48:06 +0000 |
| commit | 750a90df6ab4d119fe0fab51715464dad5ebaf2b (patch) | |
| tree | 660ebd132b13a3e87efa4addd94fbf5b0ebf4d62 /lldb/packages/Python/lldbsuite/test/functionalities/command_script/main.cpp | |
| parent | 7daec890f2b3ed17849414736de701666e2c41de (diff) | |
| download | bcm5719-llvm-750a90df6ab4d119fe0fab51715464dad5ebaf2b.tar.gz bcm5719-llvm-750a90df6ab4d119fe0fab51715464dad5ebaf2b.zip | |
ARM: maintain BB ordering when expanding WIN__DBZCHK
It is possible to have a fallthrough MBB prior to MBB placement. The original
addition of the BB would result in reordering the BB as not preceding the
successor. Because of the fallthrough nature of the BB, we could end up
executing incorrect code or even a constant pool island! Insert the spliced BB
into the same location to avoid that.
Thanks to Tim Northover for invaluable hints and Fiora for the discussion on
what may have been occurring!
llvm-svn: 264454
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/command_script/main.cpp')
0 files changed, 0 insertions, 0 deletions
