search for: creatememmove

Displaying 5 results from an estimated 5 matches for "creatememmove".

Change memcpy/memmove/memset to have dest and source alignment attributes
2018 Jan 02
5
Change memcpy/memmove/memset to have dest and source alignment attributes
...32(i8* %dest, i8* %src, i32 100, i32 4, i1 false) will now read call void @llvm.memcpy.p0i8.p0i8.i32(i8* align 4 %dest, i8* align 4 %src, i32 100, i1 false) The LLVM change includes auto upgrade of the old IR. However, match expressions in IR tests and calls to IRBuilder’s CreateMemCpy & CreateMemMove will need to be updated. My plan is to post another note to the list when the change is landed, and stable. Comments? Concerns? -Daniel --- Daniel Neilson, Ph.D. Azul Systems -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermai...
Change memcpy/memmove/memset to have dest and source alignment attributes
2018 Mar 26
1
Change memcpy/memmove/memset to have dest and source alignment attributes
...lso now invoked with different source & dest alignments by LowerMemIntrinsics, rather than the same alignment for both, so these helpers will now be invoked with more information than they have in the past; I’m guessing that it’s possible they could do better with this information. For example, createMemMoveLoop() doesn’t even use the alignments it’s given at all right now, and the neither of the createMemCpyLoop*() functions try to set the alignments on the loads & stores it creates. Passes that have conservative alignments after updating: - SelectionDAG - AArch64FastISel - ARMFastISel - MemorySa...
Change memcpy/memmove/memset to have dest and source alignment attributes
2018 Jan 18
0
Change memcpy/memmove/memset to have dest and source alignment attributes
...32(i8* %dest, i8* %src, i32 100, i32 4, i1 false) will now read call void @llvm.memcpy.p0i8.p0i8.i32(i8* align 4 %dest, i8* align 4 %src, i32 100, i1 false) The LLVM change includes auto upgrade of the old IR. However, match expressions in IR tests and calls to IRBuilder’s CreateMemCpy & CreateMemMove will need to be updated. My plan is to post another note to the list when the change is landed, and stable. Comments? Concerns? -Daniel --- Daniel Neilson, Ph.D. Azul Systems _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:...
Change memcpy/memmove/memset to have dest and source alignment attributes
2018 Apr 02
0
Change memcpy/memmove/memset to have dest and source alignment attributes
...different source & dest > alignments by LowerMemIntrinsics, rather than the same alignment for both, so > these helpers will now be invoked with more information than they have in the > past; I’m guessing that it’s possible they could do better with this > information. For example, createMemMoveLoop() doesn’t even use the alignments > it’s given at all right now, and the neither of the createMemCpyLoop*() > functions try to set the alignments on the loads & stores it creates. > > Passes that have conservative alignments after updating: > - SelectionDAG > - AArch64Fas...
Change memcpy/memmove/memset to have dest and source alignment attributes
2018 Jan 19
2
Change memcpy/memmove/memset to have dest and source alignment attributes
...4, i1 false) >> will now read >> call void @llvm.memcpy.p0i8.p0i8.i32(i8* align 4 %dest, i8* align 4 %src, i32 100, i1 false) >> >> The LLVM change includes auto upgrade of the old IR. However, match expressions in IR tests and calls to IRBuilder’s CreateMemCpy & CreateMemMove will need to be updated. >> >> My plan is to post another note to the list when the change is landed, and stable. >> >> Comments? Concerns? >> >> -Daniel >> >> --- >> Daniel Neilson, Ph.D. >> Azul Systems >> >> >>...