Displaying 6 results from an estimated 6 matches for "mayperfectlyalias".
2015 Aug 19
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
Hi All,
I'd like to float two changes to the llvm.memcpy / llvm.memmove intrinsics.
(1) Add an i1 <mayPerfectlyAlias> argument to the llvm.memcpy intrinsic.
When set to '1' (the auto-upgrade default), this argument would indicate
that the source and destination arguments may perfectly alias (otherwise
they must not alias at all - memcpy prohibits partial overlap). While the C
standard says that memcpy...
2015 Aug 19
2
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...m-dev wrote:
> Hey Lang
>> On Aug 18, 2015, at 6:04 PM, Lang Hames via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> Hi All,
>>
>> I'd like to float two changes to the llvm.memcpy / llvm.memmove intrinsics.
>>
>>
>> (1) Add an i1 <mayPerfectlyAlias> argument to the llvm.memcpy intrinsic.
>>
>> When set to '1' (the auto-upgrade default), this argument would indicate that the source and destination arguments may perfectly alias (otherwise they must not alias at all - memcpy prohibits partial overlap). While the C standard...
2015 Aug 19
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...gt;>> <llvm-dev at lists.llvm.org> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> I'd like to float two changes to the llvm.memcpy / llvm.memmove
>>>> intrinsics.
>>>>
>>>>
>>>> (1) Add an i1 <mayPerfectlyAlias> argument to the llvm.memcpy
>>>> intrinsic.
>>>>
>>>> When set to '1' (the auto-upgrade default), this argument would
>>>> indicate that the source and destination arguments may perfectly
>>>> alias (otherwise they must not al...
2015 Aug 20
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...oper via llvm-dev wrote:
>
> Hey Lang
>
> On Aug 18, 2015, at 6:04 PM, Lang Hames via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>
> Hi All,
>
> I'd like to float two changes to the llvm.memcpy / llvm.memmove
> intrinsics.
>
>
> (1) Add an i1 <mayPerfectlyAlias> argument to the llvm.memcpy
> intrinsic.
>
> When set to '1' (the auto-upgrade default), this argument would
> indicate that the source and destination arguments may perfectly
> alias (otherwise they must not alias at all - memcpy prohibits
> partial overlap). While th...
2015 Aug 21
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...; > On Aug 18, 2015, at 6:04 PM, Lang Hames via llvm-dev
> > < llvm-dev at lists.llvm.org > wrote:
> >
> > Hi All,
> >
> > I'd like to float two changes to the llvm.memcpy / llvm.memmove
> > intrinsics.
> >
> >
> > (1) Add an i1 <mayPerfectlyAlias> argument to the llvm.memcpy
> > intrinsic.
> >
> > When set to '1' (the auto-upgrade default), this argument would
> > indicate that the source and destination arguments may perfectly
> > alias (otherwise they must not alias at all - memcpy prohibits
> &...
2015 Sep 08
2
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...s via llvm-dev
> > > < llvm-dev at lists.llvm.org > wrote:
> > >
> > > Hi All,
> > >
> > > I'd like to float two changes to the llvm.memcpy / llvm.memmove
> > > intrinsics.
> > >
> > >
> > > (1) Add an i1 <mayPerfectlyAlias> argument to the llvm.memcpy
> > > intrinsic.
> > >
> > > When set to '1' (the auto-upgrade default), this argument would
> > > indicate that the source and destination arguments may perfectly
> > > alias (otherwise they must not alias at all...