search for: opus4

...pute data volumes for in and out. One of the first ideas was to use a kind of configuration file, since the kernel developer knows about the data directions. But I think this can be done more elegant. Anyway, based on your answer I'll maybe go back to this idea. Thanks, Sebastian [4] http://opus4.kobv.de/opus4-zib/files/1556/kdv_dressler_steinke_zibreport.pdf > Hope it helps, > - D. > > 2013/1/9 Sebastian Dreßler <dressler at zib.de> > >> Hi, >> >> suppose the following C function declaration: >> >> void f(int *in, int *out); >&gt...

...was to use a > kind of configuration file, since the kernel developer knows about the > data directions. But I think this can be done more elegant. Anyway, > based on your answer I'll maybe go back to this idea. > > > Thanks, > Sebastian > > > [4] > > http://opus4.kobv.de/opus4-zib/files/1556/kdv_dressler_steinke_zibreport.pdf > > > Hope it helps, > > - D. > > > > 2013/1/9 Sebastian Dreßler <dressler at zib.de> > > > >> Hi, > >> > >> suppose the following C function declaration: > >>...

Hi Sebastian, This kind of analysis is a pretty complex problem in general case. Consider, for instance, function "f" has nested calls of other functions with "side effects", meaning they could potentially change the contents of "in" or "out" indirectly. For this reason, even current state-of-art commercial APIs that imply strong data analysis (like OpenACC

Hi, suppose the following C function declaration: void f(int *in, int *out); Now further suppose, that _in_ is an array only read from and _out_ is an array that is only written to. Based on this, I was wondering whether there is some already existing LLVM pass (or maybe a part of a pass) that detects those "data directions" for pointers. I'm not quite sure whether e.g. Alias