diff options
| author | Shuxin Yang <shuxin.llvm@gmail.com> | 2013-04-08 22:00:43 +0000 |
|---|---|---|
| committer | Shuxin Yang <shuxin.llvm@gmail.com> | 2013-04-08 22:00:43 +0000 |
| commit | 331f01dcb45159b8dee5a99cf1ae29ae7dd10f39 (patch) | |
| tree | 3a1022d5afc6feb178ddbe6c71204beb4976d7d2 /clang/test | |
| parent | 0d9b3191f6956db648140b649eea79f0a5271aa1 (diff) | |
| download | bcm5719-llvm-331f01dcb45159b8dee5a99cf1ae29ae7dd10f39.tar.gz bcm5719-llvm-331f01dcb45159b8dee5a99cf1ae29ae7dd10f39.zip | |
Redo the fix Benjamin Kramer committed in r178793 about iterator invalidation in Reassociate.
I brazenly think this change is slightly simpler than r178793 because:
- no "state" in functor
- "OpndPtrs[i]" looks simpler than "&Opnds[OpndIndices[i]]"
While I can reproduce the probelm in Valgrind, it is rather difficult to come up
a standalone testing case. The reason is that when an iterator is invalidated,
the stale invalidated elements are not yet clobbered by nonsense data, so the
optimizer can still proceed successfully.
Thank Benjamin for fixing this bug and generously providing the test case.
llvm-svn: 179062
Diffstat (limited to 'clang/test')
0 files changed, 0 insertions, 0 deletions
