search for: aviral

Displaying 4 results from an estimated 4 matches for "aviral".

Did you mean: avira
2018 Jan 03
3
Coping with non-standard evaluation in R program analysis
Hello R experts, I plan to develop a tool for dynamic analysis of R programs. I would like to trace function calls at runtime, capturing argument and return values. Following a suggestion made some time ago on this list, my high-level implementation strategy is to rewrite the AST, augmenting call expressions with pre-call and post-call shims to capture the arguments and return value,
2018 Jan 04
0
Coping with non-standard evaluation in R program analysis
...genthat We don?t really deal with NSE though. It could be something worth thinking about for us. The contact for genthtat is Filip. We are also writing a tool for analyzing promises and generating execution traces within the R VM. This is available in https://github.com/PRL-PRG/R-dyntrace Aviral and Konrad are the contacts there. Best, jan Jan Vitek, Professor Computer Science, Northeastern University > On Jan 3, 2018, at 7:18 PM, Peter Meilstrup <peter.meilstrup at gmail.com> wrote: > > For 2), it is not exposed in R's standard library but it is exposed in...
2019 Mar 02
2
Support for out-of-tree backend passes?
...pass builds? Similarly, would work in the direction of supporting those builds be welcome? If so, it's something I'd like to look at. Best, William Woodruff william at yossarian.net [1]: https://github.com/samolisov/llvm-experiments/tree/master/llvm-backend-x86-machine-passes [2]: http://aviral.lab.asu.edu/llvm-writing-a-backend-pass/ [3]: (Thread) https://lists.llvm.org/pipermail/llvm-dev/2015-November/092030.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <h...
2015 Jun 10
4
[LLVMdev] The use iterator not working...
Thanks Dan and Jon. I made an incorrect assumption that the "use" iterator was actually giving me the "user" when de-referencing it. Did it always have this behavior in previous LLVM versions? I've seen lots of examples of the "use" iterator being dereferenced and resulting Instruction pointer being treated as the "user"? Thanks, Zack On Tue, Jun 9,