Displaying 4 results from an estimated 4 matches for "issrcvolatile".
2015 Aug 20
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...ut we teach clang,
SimplifyLibCalls, etc. to add noalias metadata where we know it's safe.
Dropping the alignment argument will still change the signature of
llvm.memcpy / llvm.memmove, so I guess there's one other issue worth
discussing: Should we also split 'isVolatile' into 'isSrcVolatile' and
'isDstVolatile' ? Nobody has asked for this as far as I know, but I believe it
would improve codegen in some cases. E.g.:
typedef struct {
unsigned X[8];
} S;
unsigned foo(volatile S* s) {
S t = *s;
return t.X[4];
}
If the frontend lowers the struct copy to a volatile memc...
2015 Aug 21
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...any existing metadata with the correct semantics.
>
> >
> > Dropping the alignment argument will still change the signature of
> > llvm.memcpy / llvm.memmove, so I guess there's one other issue worth
> > discussing: Should we also split 'isVolatile' into 'isSrcVolatile'
> > and 'isDstVolatile' ?
>
> Yes. We should be able to specify all relevant properties of the source
> and destination separately. I see no reason not to do this.
>
> -Hal
>
> > Nobody has asked for this as far as I know,
> > but I believe it would...
2015 Sep 08
2
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
...semantics.
> >
> > >
> > > Dropping the alignment argument will still change the signature of
> > > llvm.memcpy / llvm.memmove, so I guess there's one other issue
> > > worth
> > > discussing: Should we also split 'isVolatile' into 'isSrcVolatile'
> > > and 'isDstVolatile' ?
> >
> > Yes. We should be able to specify all relevant properties of the
> > source and destination separately. I see no reason not to do this.
> >
> > -Hal
> >
> >
> >
> > > Nobody has asked...
2015 Aug 19
3
[RFC] Generalize llvm.memcpy / llvm.memmove intrinsics.
> On Aug 19, 2015, at 12:01 PM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> ----- Original Message -----
>> From: "Philip Reames via llvm-dev" <llvm-dev at lists.llvm.org>
>> To: "Pete Cooper" <peter_cooper at apple.com>, "Lang Hames" <lhames at gmail.com>
>> Cc: "LLVM Developers Mailing