similar to: [LLVMdev] Dynamic Profiling - Instrumentation basic query

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

On 1/13/13 11:06 PM, Criswell, John T wrote: > There is code that does this for older versions of LLVM. I believe it is in the giri project in the LLVM SVN repository. I can look into more details when I get back from vacation. Swarup may also be able to provide information on the giri code. I took a quick look, and the dynamic slicing code doesn't appear to be checked into the giri

There is code that does this for older versions of LLVM. I believe it is in the giri project in the LLVM SVN repository. I can look into more details when I get back from vacation. Swarup may also be able to provide information on the giri code. -- John T. ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Silky Arora

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:

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:

Hi, @Alastair: Thanks a bunch for explaining this so well. I was able to write a simple profiler, and run it. I need to profile the code for branches (branch mis predicts simulation), load/store instructions (for cache hits/miss rate), and a couple of other things and therefore, would need to instrument the code. However, I would like to know if writing the output to a file would increase the

Hi Alastair, Thank you so much for the information on the tools. Actually, I need to analyze which sections of code are prone to misses and mis predicts, and would have to eventually instrument the code. I was able to instrument and call an external function, but faced an issue while passing an argument to the function. I am following EdgeProfiling.cpp but couldn't figure out the problem.

Hi Silky, Sorry for the slow reply. You probably already fixed this, but just in case I'll reply anyway. Comments inline below On 15/01/13 19:38, SArora wrote: > Hi Alastair, > Thank you so much for the information on the tools. Actually, I need to > analyze which sections of code are prone to misses and mis predicts, and > would have to eventually instrument the code. >

Thanks Renato and Giang. I was able to run a simple HelloWorld program on gem5 (in SE mode) by using -target -arm-none-linux-gnueabi as the option during cross compilation. I am trying to cross compile some Computer Vision algorithms, which use OpenCV libraries, and I tried using the same command line options - clang++ *-emit-llvm -static -c -Wall -g -O0 -mfpu=vfp -mfloat-abi=soft

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. ________________________________

Hi, I am trying to optimize some benchmarks using LLVM and run them on gem5 simulator (build for ARM). I am using Sourcery Codebench cross-compiler for ARM on my x-86 machine. My steps up till now have been using the following commands. 1. clang -static -emit-llvm -march=armv7-a -mfloat-abi=soft -target arm-elf a.cpp -c -integrated-as \

Hi Silky, On 14/01/13 01:47, Silky Arora wrote: > I need to profile the code for branches (branch mis predicts > simulation), load/store instructions (for cache hits/miss rate), and a > couple of other things and therefore, would need to instrument the code. > However, I would like to know if writing the output to a file would > increase the execution time, or is it the profiling

Hi Jin Huang, The updated Giri code is available at https://github.com/liuml07/giri<https://github.com/liuml07/giri.>. This will give you an idea of how to instrument the program to trace different values. You can modify the code to achieve your goals. -Swarup. ________________________________ From: Criswell, John T Sent: Thursday, January 02, 2014 2:12 PM To: Jin Huang; llvmdev at

Thank you , James. But this way needs to determine whether the instruction is a LOAD/STORE ,and if I want to preserve the operations on these variables for further dynamic symbolic execution usage(just like KLEE ,but it's a static analysis ,not dynamic),I had to backtrace instructions ,this may be not very efficient if the operation is very complex! -Jin Huang 2014/1/3 Jin Huang

You will have to insert callinst to tracing functions immediately after the value is produced, not at the entry points. Giri code has many such examples of how to do this. Thanks, Swarup. ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Jin Huang [54jin.huang at gmail.com] Sent: Thursday, January 02, 2014 9:47 PM To: llvmdev at

On 17 March 2013 22:40, SArora <silkyar at umich.edu> wrote: > However, this errors out saying > > > /home/silky/VecProject/opencv/OpenCVInstall/arm/include/opencv2/core/mat.hpp:117:9: > error: cannot compile this atomic library call yet > CV_XADD(refcount, 1); > ^~~~~~~~~~~~~~~~~~~~ > >

One can use "-insert-edge-profiling" with opt to collect general metrics (frequency of function execution, frequency of basic block execution). But I'd like to record all call information. So every time a function call is made, I'd like to record [calling function name, callee function name] Is this feasible with with llvm-prof and any of the existing profiling options?

Hi, everyone. I want to writing a Pass to get the variable value while the program is running ,the basic idea is to insert an STL map in the program ,and get every value and address a program use ,but whether it's possible to do this by transforming the llvm IR? I didn't find any useful functions to get a variable's address in LLVM IR .It seems that the IR is an SSA form and we can

Hi, I want to find the dynamic slice of a given code. Is this already implemented in LLVM?. If not which functions are there in the LLVM to do dynamic analysis.

Dear all, I have already checked some related posted messages, such as: http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-January/012315.html and http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-February/012466.html After getting rid of some error messages, I was able to run the following commands: 1) opt -insert-path-profiling matmul.bc -o matmul.pp.bc 2) lli -load