diff options
| author | Tobias Grosser <tobias@grosser.es> | 2015-12-15 23:50:01 +0000 |
|---|---|---|
| committer | Tobias Grosser <tobias@grosser.es> | 2015-12-15 23:50:01 +0000 |
| commit | 184a4926b3f6740ecf4caa97b965ecf883ddf0eb (patch) | |
| tree | a7bc0765d6b184a3a23b4d7764fb3f0263cd76f2 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py | |
| parent | a69d4f0d83a15e2d2e26d0e2a109693b7138b334 (diff) | |
| download | bcm5719-llvm-184a4926b3f6740ecf4caa97b965ecf883ddf0eb.tar.gz bcm5719-llvm-184a4926b3f6740ecf4caa97b965ecf883ddf0eb.zip | |
BlockGenerator: Use getArrayAccessFor for vector code generation
getAccessFor does not guarantee a certain access to be returned in case an
instruction is related to multiple accesses. However, in the vector code
generation we want to know the stride of the array access of a store
instruction. By using getArrayAccessFor we ensure we always get the correct
memory access.
This patch fixes a potential bug, but I was unable to produce a failing test
case. Several existing test cases cover this code, but all of them already
passed out of luck (or the specific but not-guaranteed order in which we build
memory accesses).
llvm-svn: 255715
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py')
0 files changed, 0 insertions, 0 deletions
