similar to: [LLVMdev] Problems with instrumentation

Hi, I need to instrument the code in order to generate an event (call a certain function) whenever X instructions have been executed. I'm using MachineFunctionPass to get machine-dependent representation of each LLVM function in the program. However, such pass doesn't allow to modify such functions. Is there any other class so I can modify MachineFunctions? Thanks in advance, Raul. --

Hi, > llvm-gcc -g -emit-llvm test.c -c -o test.bc > opt -insert-edge-profiling test.bc -o output.bc > llc output.bc -o output.s > gcc output.s -o test.out > > However, it can't find symbol llvm_start_edge_profiling. -insert-edge-profiling inserts call to the llvm_start_edge_profiling function which is a part of a profiling runtime library. This library must be linked

Hi, Could anyone tell me how exactly can one convert a .bc file (bitcode file) to an executable in the native program. I was trying an instrumentation transform with the following workflow opt -insert-edge-profiling input.bc -o output.bc and then try and execute output.bc using lli output.bc however the program gives the following error : Program used external function

Hi all I want to use "'/home/llvm/src/utils/profile.pl' -edge sort.bc" command, but i face this error: Error opening '/usr/local/lib/profile_rt.so': /usr/local/lib/profile_rt.so: cannot open shared object file: No such file or directory -load request ignored. LLVM ERROR: Program used external function 'llvm_start_edge_profiling' which could not be resolved!

Hi, I was able to figure out this one, by checking out profile.pl. However, I am still interested in getting to know if there is anyway to compile from bitcode to a normal executable? Maybe I am missing something obvious... :P ? Thanks Nipun On Fri, Apr 1, 2011 at 1:34 PM, Nipun Arora <nipun2512 at gmail.com> wrote: > Hi, > > Could anyone tell me how exactly can one convert a

Thanks for your reply. May I know which is the recommended library that should be linked against? I am currently linking libprofile_rt.a. And I have noticed the differences that, if we do `nm libprofile_rt.a | grep llvm` with my old copy of the llvm/clang installation, I can see 00000000000005e0 T _llvm_gcda_emit_arcs 0000000000000b48 S _llvm_gcda_emit_arcs.eh 0000000000000430 T

Hi Terence, On 2008-04-20, at 20:08, Terence Parr wrote: > I've exhausted what I can do on my own to make a GC example bind > (usual googling, reading, playing, looking at source). I can't find > the shadow collector lib or perhaps the -l options needed to link my > sample (not even to point where I'm figuring out GC actually as I > can't link). The shadow

Howdy do LLVM folks! I've exhausted what I can do on my own to make a GC example bind (usual googling, reading, playing, looking at source). I can't find the shadow collector lib or perhaps the -l options needed to link my sample (not even to point where I'm figuring out GC actually as I can't link). Not sure this IR is correct but here is what I've been playing

I have a file in the following format: Scenario1 Scenario1CIL Scenario1CIU Scenario2 Scenario2CIL Scenario2CIU 60 57 62 45 48 50 110 101 111 51 50 52 120 117 122 64 62 66 192 190 194 79 75 79 where: First column = Scenario1 mean value Second column = Scenario1 Low Confidence Interval Third column = Scenario1 Upper Confidence Interval Fourth column = Scenario2 mean value Fifth column =

On Tue, Oct 26, 2004 at 11:17:00PM -0500, Chris Lattner wrote: > On Tue, 26 Oct 2004, Tom Brown wrote: > > $ llvm-as alloc_loop.ll > > $ lli alloc_loop.bc > > lli: Globals.cpp:81: llvm::GlobalVariable::GlobalVariable(const llvm::Type*, bool, llvm::GlobalValue::LinkageTypes, llvm::Constant*, const std::string&, llvm::Module*): Assertion `Initializer->getType() == Ty

I'm in a group tasked with improving the GC of LLVM for a 421 project. We are having trouble getting started with the given SemiSpace collector. We found the string llvm_gc_initialize called from a single source file ./test/Regression/CodeGen/Generic/GC/alloc_loop.ll which we tried with the following... (showing LLVM checked out from cvs a few days ago, similar output with release 1.3) $

On Fri, Mar 15, 2013 at 1:36 AM, Qun Fa <testforqunfa at gmail.com> wrote: > Hi All, > > I think Nick's suggestion is correct, my code was linked against > libprofile_rt.a, which had gcda profiling code before, but was removed > https://github.com/llvm-mirror/llvm/commit/218042a02305a3cc38d968a97ff9ecf4b4abe6ff > > So, I couldn't find the correct symbols from

Hi All, I think Nick's suggestion is correct, my code was linked against libprofile_rt.a, which had gcda profiling code before, but was removed https://github.com/llvm-mirror/llvm/commit/218042a02305a3cc38d968a97ff9ecf4b4abe6ff So, I couldn't find the correct symbols from libprofile_rt.a any more. Now my assumption is I need to use the correct library that is provided by compiler-rt.

On Tue, 26 Oct 2004, Tom Brown wrote: > I'm in a group tasked with improving the GC of LLVM for a 421 project. > We are having trouble getting started with the given SemiSpace > collector. > > We found the string llvm_gc_initialize called from a single source file > ./test/Regression/CodeGen/Generic/GC/alloc_loop.ll > which we tried with the following... (showing LLVM

Hi! On Fri, Mar 15, 2013 at 10:51 PM, Qun Fa <testforqunfa at gmail.com> wrote: > Thank you Alexey. > > I have tried to use Makefile. This will generate the correct symbols that > I need. > > Any idea on the schedule of adding CMake support to compiler-rt? > Starting from r177382 CMake on Linux should build the same profile compiler-rt library as Makefiles. >

On Wed, 27 Oct 2004, Tom Brown wrote: > On Tue, Oct 26, 2004 at 11:17:00PM -0500, Chris Lattner wrote: > > On Tue, 26 Oct 2004, Tom Brown wrote: > > > $ llvm-as alloc_loop.ll > > > $ lli alloc_loop.bc > > > lli: Globals.cpp:81: llvm::GlobalVariable::GlobalVariable(const llvm::Type*, bool, llvm::GlobalValue::LinkageTypes, llvm::Constant*, const std::string&,

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In

Couple of questions: 1. void llvm_gc_write(void *V, void *ObjPtr, void **FieldPtr) I haven't seen an adequate explanation of these, but I'm guessing: void *V: value being written to the field void *ObjPtr: current value of the field (ie. ObjPtr == *FieldPtr upon entry to llvm_gc_write) void **FieldPtr: address of the field being written 2. The current semispace collector includes

Thank you Alexey. I have tried to use Makefile. This will generate the correct symbols that I need. Any idea on the schedule of adding CMake support to compiler-rt? Sincerely, Qun On Fri, Mar 15, 2013 at 1:51 AM, Alexey Samsonov <samsonov at google.com>wrote: > > On Fri, Mar 15, 2013 at 1:36 AM, Qun Fa <testforqunfa at gmail.com> wrote: > >> Hi All, >>

On Apr 20, 2008, at 5:36 PM, Gordon Henriksen wrote: > The shadow stack walker is in the runtime directory with the semispace > heap example. The runtime directory is built to LLVM IR using llvm- > gcc. So it's skipped unless you configure llvm with llvm-gcc support. doh! That's how I missed the binary. thanks! > Since the semispace heap doesn't actually work (it's