Displaying 4 results from an estimated 4 matches for "promotememcpi".
Did you mean:
promotememcpy
2018 Feb 01
0
llvm.memcpy for struct copy
On 31 Jan 2018, at 17:36, Jakub (Kuba) Kuderski via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> If you want to get rid of memcpy altogether, you can take a look at this pass: https://github.com/seahorn/seahorn/blob/master/lib/Transforms/Scalar/PromoteMemcpy.cc .
There are at least four different places in LLVM where memcpy intrinsics are expanded to either sequences of
2018 Jan 31
4
llvm.memcpy for struct copy
Hi Ma,
how can I transform the llvm.memcpy into data move loop IR and eliminate
> the bitcast instruction ?
>
I'm not sure why you are concerned about memcpy and bitcasts, but if you
call MCpyInst->getSource() and MCpyInst->getDest() it will look through
casts and give you the 'true' source/destination.
If you want to get rid of memcpy altogether, you can take a look
2018 Jan 30
0
llvm.memcpy for struct copy
Hi Craig
Thank you very much !
2018-01-30 16:11 GMT+08:00 Craig Topper <craig.topper at gmail.com>:
> The pointers must always be i8* the alignment is independent and is
> controlled by the attributes on the arguments in the call to memcpy.
>
> ~Craig
>
> On Mon, Jan 29, 2018 at 11:45 PM, ma jun <jun.parser at gmail.com> wrote:
>
>> Hi
>>
>>
2018 Jan 30
2
llvm.memcpy for struct copy
The pointers must always be i8* the alignment is independent and is
controlled by the attributes on the arguments in the call to memcpy.
~Craig
On Mon, Jan 29, 2018 at 11:45 PM, ma jun <jun.parser at gmail.com> wrote:
> Hi
>
>
> 2018-01-30 15:36 GMT+08:00 ma jun <jun.parser at gmail.com>:
>
>> Hi
>> Thanks !
>> so for this example
>>