similar to: [LLVMdev] GSoC Proposal: Inter-Procedure Program Slicing in LLVM

Hi all, This is a GSoC 2013 proposal for LLVM project. Please see the formatted version at here: http://pacman.cs.tsinghua.edu.cn/~liuml07/files/gsoc2013-proposal-program-slicing.pdf Program slicing has been used in many applications, the criteria of which is a pair of statement and variables. I would like to write an inter-procedural program slicing pass in LLVM, which is able to calculate C

Hi, 1. How can I report a bug or commit a patch to the giri progject? I doubt this central commit list is the right place. 2. Are you still maintaining the giri project any more? Thank you. L On Thu, Jun 28, 2012 at 12:49 AM, John Criswell <criswell at illinois.edu>wrote: > On 6/26/12 5:07 PM, amruth.rd wrote: > > Hello, > > > > I am curious to know if

On 5/1/13 11:36 PM, Mingliang LIU wrote: > Hi all, > > I had a second thought of the dynamic slicing, as well as the source > code generating. > > Firstly, the dynamic slicing is very useful to software community > (I'll illustrate more in the refined proposal later), but it's already > implemented by Swarup and John Criswell from UIUC. The static slicing >

Hi all, This is a GSoC 2013 proposal for LLVM project. Please see the formatted version at here: http://pacman.cs.tsinghua.edu.cn/~liuml07/files/gsoc2013-proposal-program-slicing.pdf Program slicing has been used in many applications, the criteria of which is a pair of statement and variables. I would like to write an inter-procedural program slicing pass in LLVM, which is able to calculate C

John, Thanks for your quick reply. Firstly, I'd like to employ a slicer for our benchmarking work (in one word, reducing the long-time irrelevant computing). I find the giri project and the LLVMSlicer[1]. However, the giri doesn't seem a complete implementation to me. I admit that I have not finished reading document/discussion, e.g. the previous threads in this mailing list. While the

On 6/26/12 5:07 PM, amruth.rd wrote: > Hello, > > I am curious to know if LLVM offers any passes to do interprocedural slicing, I need to eliminate most of the computations(possibly all, if they don't influence the control flow), but the control flow of the program should be maintained at all cost. I did see an optimization pass to print the CFG of a function without its body to a

Hello, I am curious to know if LLVM offers any passes to do interprocedural slicing, I need to eliminate most of the computations(possibly all, if they don't influence the control flow), but the control flow of the program should be maintained at all cost. I did see an optimization pass to print the CFG of a function without its body to a dot file, but I am interested in generating the

Dear John, Now, I want to do dynamic analysis by dynamic slicing based on LLVM. I just see that you have implemented dynamic slicing for LLVM. I also check the Giri project, and I don't find the code. I hope I can learn something from your code. I am very appreciated if you can tell me how to get the code or send me one copy. Thank you very much! Pengfei -- View this message in context:

Hi Pengfei, Glad you tried the program and it works fine to you for the first place. Dr. Swarup and John from UIUC wrote most of the code, and released the original code to public. Dynamic slicing tool is really very useful. Giri is now far from perfect. For example, there are know bugs for multi-thread programs and I'm fixing it these weeks. I will take charge of this project for a while

Yes, the latest version can be downloaded from here https://github.com/liuml07/giri . The LLVM instrumentation code is in TracingNoGiri.cpp<https://github.com/liuml07/giri/blob/master/lib/Giri/TracingNoGiri.cpp> file and runtime code in Tracing.cpp. You may need to delete other unnecessary instrumentation code which you don't need. Thanks, Swarup. ________________________________

Hello John, Thank you for your advices and congratulations~ I'll read the code of cfl-aa and Giri first and make the decision of which project to pursue. The choice will be reported to this thread once I made the determination (hopefully within this week). Thanks! On 3 March 2015 at 23:12, John Criswell <jtcriswel at gmail.com> wrote: > Dear Mingxing, > > I think both

Wow, that is cool! I'll check about it. Thank you! On 4 March 2015 at 21:57, John Criswell <jtcriswel at gmail.com> wrote: > On 3/4/15 2:18 AM, Mingxing Zhang wrote: > > Hello John, > > Thank you for your advices and congratulations~ > > I'll read the code of cfl-aa and Giri first and make the decision of which > project to pursue. > The choice will be

On 3/8/15 8:56 AM, Mingxing Zhang wrote: > Hello John, > > According to the FAQ, I can submit two proposals although at most one > of them can be accepted. > Thus I will prepare a proposal for each of the two projects. Correct. Only one proposal will be accepted. > And, after reading the code of cfl-aa and several related papers, I've > listed four milestones for the

Hi, maybe you can have a look at the CReduce project: http://embed.cs.utah.edu/creduce/ This project implements many source-to-source transformations of C programs, e.g. removing functions, changing variable names, deleting branches in if-statements, etc. Some of these are purely based on the source code, other use the Clang frontend. Hope this helps, Jonas On Sun, Mar 17, 2013 at 7:25 PM,

Hello John, I've finished the first version of my proposal on enhancing alias analysis. The proposal can be downloaded at http://james0zan.github.io/resource/GSoC15-Proposal-AA.pdf. I hope I've successfully justified the necessity and benefits of this project. If possible, please find some time to review it and give me some more feedbacks. Thank you very much! P.S. I'm working on

Hi all, I'm doing the program slicing [1] in LLVM. Now I implemented the Weiser's algorithm [2] in a simple way by writing a plugin to analyze the IR. My final goal is to slice the source code, thus I recorded all the lines of source code to be sliced. The last step is to delete the lines which are not in the program slice. However, I met a problem when deleting the source code directly:

On 1/22/13 12:07 PM, Sahoo, Swarup Kumar wrote: > Hi John and Silky, > > I can see a copy of 'giri' slicing project branch here http://llvm.org/viewvc/llvm-project/giri/. Though it may be little older, it will work I think. You can look at the code to see how we do the instrumentation. The giri project is supposed to contain both the static slicing code and the dynamic

Oh, OK. I didn't check the code. I think it only contains your flow tracking analysis code, isn't it. Our 'Giri' project was completely separate from it. Should we merge it with this or keep it as a separate project? -Swarup. ________________________________________ From: John Criswell [criswell at illinois.edu] Sent: Tuesday, January 22, 2013 12:12 PM To: Sahoo, Swarup Kumar Cc:

On 10/9/11 12:12 AM, Jinwook Shin wrote: > Thanks John. I appreciate your help and I look forward to obtaining the code. > > A proper LLVM sub-project: No rush on this and please take your time. Thanks. Okay, I've created a new LLVM sub-project called Giri(*). It currently contains only the static backwards slicing pass. I'll add the dynamic slicing code to the project later.

Hi John and Silky, I can see a copy of 'giri' slicing project branch here http://llvm.org/viewvc/llvm-project/giri/. Though it may be little older, it will work I think. You can look at the code to see how we do the instrumentation. Thanks, Swarup. ________________________________________ From: John Criswell [criswell at illinois.edu] Sent: Tuesday, January 22, 2013 10:29 AM To: