summaryrefslogtreecommitdiff
path: root/llvm.spec.in
diff options
context:
space:
mode:
authorPawel Wodnicki <pawel@32bitmicro.com>2012-12-10 14:20:28 +0000
committerPawel Wodnicki <pawel@32bitmicro.com>2012-12-10 14:20:28 +0000
commit3f0b779be8218760033ad0ff698ea88c3c7e73c9 (patch)
tree7855324f577c0b6cc329780ff0feb491303fba63 /llvm.spec.in
parent710e1c519ac303c54015c9d8e9f7e28c76f82d41 (diff)
downloadllvm-3f0b779be8218760033ad0ff698ea88c3c7e73c9.tar.gz
llvm-3f0b779be8218760033ad0ff698ea88c3c7e73c9.tar.bz2
llvm-3f0b779be8218760033ad0ff698ea88c3c7e73c9.tar.xz
Merging r169719: into 3.2 release branch.
Fix PR14548: SROA was crashing on a mixture of i1 and i8 loads and stores. When SROA was evaluating a mixture of i1 and i8 loads and stores, in just a particular case, it would tickle a latent bug where we compared bits to bytes rather than bits to bits. As a consequence of the latent bug, we would allow integers through which were not byte-size multiples, a situation the later rewriting code was never intended to handle. In release builds this could trigger all manner of oddities, but the reported issue in PR14548 was forming invalid bitcast instructions. The only downside of this fix is that it makes it more clear that SROA in its current form is not capable of handling mixed i1 and i8 loads and stores. Sometimes with the previous code this would work by luck, but usually it would crash, so I'm not terribly worried. I'll watch the LNT numbers just to be sure. git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_32@169735 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'llvm.spec.in')
0 files changed, 0 insertions, 0 deletions