[PATCH] Fix two issues on unaligned 256-bit vector memory access on AVX

[Michael Liao]

ping again with patches re-attached. - michael

On Sat, 2013-03-23 at 22:07 -0700, Michael Liao wrote:
> Hi All
> 
> On Sandybridge, unaligned 256-bit vector memory access needs splitting
> to avoid higher cache line split penalty. The 1st patch enhances ToT to
> handle non <4 x i64> vector integer types. The 2nd patch fixes two
> alignment calculation issues in ToT. One is a memory access is regarded
> as aligned if the specified alignment is larger than the natural
> alignment; the other issue is that the alignment for the high 128-bit
> vector should be min(16, original alignment) since the pointer is
> advanced by 16B, a power-of-2 offset.
> 
> Test cases are included for each patch.
> 
> Thanks for review
> - Michael
> 
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Enhance-folding-of-extract_subvec-insert_subvec-V1-V.patch
Type: text/x-patch
Size: 4695 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130325/9675f81c/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Revise-alignment-calculation-issues-on-256-bit-unali.patch
Type: text/x-patch
Size: 4950 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130325/9675f81c/attachment-0001.bin>