similar to: [LLVMdev] How to insert a self-written function to a piece of programme

My friends, I ran a function pass on a .bc file, intending to insert a CallInst to my self-made check function. The compilation is successful. BUT after I ran that pass on the .bc file, the size of the file didn't get any bigger!! Does this mean my instrumentation work failed?? BTW the opt command I use is "opt -load ../../../Debug+Asserts/lib/Hello.so -hello <hello.bc> -o

I figured that my opt command is wrong! How to specify the output file anyway?? if I want hello.bc to be input file and newhello.bc to be output file, is the opt command go like this? opt -load ../../../Debug+Asserts/lib/Hello.so -hello <hello.bc> -o newhello.bc ?? -- 祝好！ 甄凯

Hi, I don't think the code you pasted can be the correct code, where does FibF come from? Anyway, the problem is that you're calling the FibF from Module A, however you defined it for Module B. You need to insert the FibF function into the Module that you're running. To do this override "virtual bool doInitialization(Module &M);" and insert FibF into M. Joey 2012/4/9

Thank you very much! To make it simpler, I may as well just implement the self-written "check function" in C language instead of wrapping it in LLVM module. According to the hint you give me, all I need to do is as follow(?) 1. Implement the "Check function" in the check.c file; 2. Add the check function into the module(the Hello1.bc file which I will run the functionPass on)

That sounds like a good general plan, yes! Joey 2012/4/9 15102925731 <zhenkaixd at 126.com> > Thank you very much! > > To make it simpler, I may as well just implement the self-written "check > function" in C language instead of wrapping it in LLVM module. *According > to the hint you give me, all I need to do is as follow(?)* > > 1. Implement the

Hi all， Im trying to instrument this hello function right before the instruction that call the "puts" function(the source code is as follow). Now I can compile the pass without errors, but when run the pass with opt tool, it broke down. The diagnose is something like Referencing function in another module! %CallCheck = call i32 @fib() Broken module found, compilation aborted! Does

Hi, I got upset.. What does “Broken module found, compilation aborted!” mean really?? what‘s “broken module“?? -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-09 ------------------------------------------------------------------------------------------------------ Name: 甄凯(ZhenKai)

Thanks for your reply! I send the message to the mail list this time~ Did you mean I need to initialize M and the Context? Is that really necessary? Does all the function need to be wrapped in the module? I remember you once said "you can just declare the function (i.e. no need to give it a body), and call it.You can then link with an object file that defines it. This is simpler than

Your files do not appear to implement the check() function. On Tue, Apr 10, 2012 at 4:57 PM, 15102925731 <zhenkaixd at 126.com> wrote: > Hi, my friends > > I finally insert the callInst into the hello.bc file.Then I compile the > hello.bc to hello.o file and the check.c to check.o file. And I think by > link those to .o file togetherI can get the executable ELF file(clang

Hi, my friends I finally insert the callInst into the hello.bc file.Then I compile the hello.bc to hello.o file and the check.c to check.o file. And I think by link those to .o file togetherI can get the executable ELF file(clang hello.o check.o -o finalfile). But when I link the two objective file, it said "hello.o: In function `main': hello.bc:(.text+0x69): undefined reference to

I did it !!!! YOU MADE MY DAY !!!!!!!!!!!!!!! -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-10 ------------------------------------------------------------------------------------------------------ Name: 甄凯(ZhenKai) Homepage:http://www.renren.com/262729393 Email: zhenkaixd at 126.com or 846227103 at

I may try to use the Makefile then. When using gcc the Makefile is CC := colorgcc obj-m := hello.o KERNELDIR := /lib/modules/2.6.36.1/build PWD := $(shell pwd) modules: $(MAKE) -C $(KERNELDIR) M=$(PWD) modules #modules install: # $(MAKE) -C $(KERNELDIR) M=$(PWD) modules_install How to change it so the generating result is .bc file not the .o file? PLEASE BE KIND AND HELP ME~~ --

Yeah, but I tried that command and error message was generated: hellomodule.c:1:10: fatal error: 'linux/init.h' file not found #include <linux/init.h> ^ 1 error generated. how to solve this problem?? Thanks! -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-12

Ok, that makes sense! That is to say, I don't need a makefile (in which to specify the path to kernel) to compile it. Just a clang command with some option will do it, right? -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-12

Dear Chen, I tried the command you told me. It turns out that clang use -I option rather then -isystem. But after I included the init.h file, it fired at me that "asm/processor.h" is not fount. Then I included that file using -I option and some other files were said not found! It's like I opened a can of worms... I can still continue to include the file that is said not found. But

Wow that's to much output information. Maybe I can put it in this way. Could you tell me the clang option that can include the linux kernel headers??? Something like "clang -O3 -isystem /lib/modules/`uname -r`/build/include -emit-llvm hellomodule.c -c -o hellomodule.bc" Thank you! -- 祝好！ 甄凯

On 4/11/12 8:25 PM, 15102925731 wrote: > Yeah, but I tried that command and error message was generated: > > hellomodule.c:1:10: fatal error: 'linux/init.h' file not found > #include <linux/init.h> > ^ > 1 error generated. > > how to solve this problem?? Well, you do have to include all the -I and -D options so that clang can find the Linux kernel header

It's actually is .c file. I just want firstly to compile helloworldmodule.c into helloworldmodule.bc. Then I run a LLVM pass on it to do some optimization, and then I compile the modified .bc file into .ko file. So, could you tell me how to compile helloworldmodule.c into helloworldmodule.bc? I think it's not the same command "clang -O3 -emit-llvm hello.c -c -o hello.bc".

Hi, Nick I think that's the question. I just don't know what's the command line that can tell clang to find the linux head file like a makefile will do. Please help me! -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-12

Hi, my friends I know there is a difference between compiling a linux module and a simple helloworld programme. If I compile a helloworld.c file, the command is "clang -O3 -emit-llvm hello.c -c -o hello.bc" But what the command should be if I want to compile a linux module into a .bc file? (I know it may be an easy question to you guys, but I really don't know where to find the