summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Bitcode
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2015-02-22 15:58:04 +0000
committerHal Finkel <hfinkel@anl.gov>2015-02-22 15:58:04 +0000
commitf5b957060bf228d03c0c288387caa81ad3508b85 (patch)
treebc6fed98b98ed514bc25eaeb555aa501468a71d1 /llvm/lib/Bitcode
parent9cbc6f42aad308de56ecae113ed8a86a86997137 (diff)
downloadbcm5719-llvm-f5b957060bf228d03c0c288387caa81ad3508b85.tar.gz
bcm5719-llvm-f5b957060bf228d03c0c288387caa81ad3508b85.zip
[SDAG] Use correct alignments on expanded vector trunc-store/ext-loads
When expanding a truncating store or extending load using vector extracts or inserts and scalar stores and loads, we were giving each of these scalar stores or loads the same alignment as the original vector operation. While this will often be right (most vector operations, especially those produced by autovectorization, have the alignment of the underlying scalar type), the vector operation could certainly have a larger alignment. No test case (yet); noticed by inspection. llvm-svn: 230175
Diffstat (limited to 'llvm/lib/Bitcode')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud