similar to: [LLVMdev] LLVM problem, please do not ignore

On 11/3/2011 4:55 AM, Arshak Nazaryan wrote: > Dear sir or madam, > > I am a 4-th year student at Yerevan State University, Armenia; and I > am studying LLVM in order to write my Bachelor thesis. Hi Arshak. > I am trying to write an llvm pass that just removes all "Add" commands > and gives some statstics. > Nevertheless, I get this segmentation fault: The

I am trying to use ExtractLoop() but I am getting segFaults: 0 opt 0x00000000008edc2f 1 opt 0x00000000008edfda 2 libpthread.so.0 0x00007ffe21203c60 3 opt 0x0000000000895ed9 llvm::Value::getName() const + 9 4 LLVMEXITCDFG.so 0x00007ffe202b80d7 5 opt 0x00000000006fc6e7 llvm::LPPassManager::runOnFunction(llvm::Function&) + 1143 6 opt

It looks like this problem only exists on nested loops, ideas? On Thu, Jan 12, 2012 at 11:44 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > Is it not a good idea to try and extract loops that have multiple exits? > > > On Thu, Jan 12, 2012 at 10:44 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > >> I am trying to use ExtractLoop() but I am getting segFaults:

Is it not a good idea to try and extract loops that have multiple exits? On Thu, Jan 12, 2012 at 10:44 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > I am trying to use ExtractLoop() but I am getting segFaults: > > 0 opt 0x00000000008edc2f > 1 opt 0x00000000008edfda > 2 libpthread.so.0 0x00007ffe21203c60 > 3 opt 0x0000000000895ed9

How do you expect people to be able to tell you if you are using it properly if they can't see how you are using it? Cameron On Jan 12, 2012, at 12:22 PM, Ryan Taylor wrote: > I'm not sure it's a bug. If I don't know if I am properly using it then how would I know it's a bug and not simply a user issue? If it sounds like a bug to you then I will file it. :) > > On

---------- Forwarded message ---------- From: Ryan Taylor <ryta1203 at gmail.com> Date: Thu, Jan 12, 2012 at 12:22 PM Subject: Re: [LLVMdev] Extract Loop Failing To: Cameron Zwarich <zwarich at apple.com> I'm not sure it's a bug. If I don't know if I am properly using it then how would I know it's a bug and not simply a user issue? If it sounds like a bug to you then

On Wed, 9 Jun 2004, Vladimir Prus wrote: > > I assume that the two unconditional gotos are just test code, right? If > > not, the second one is dead. > > Yes, in the final form there will be "iflt" instruction before the first goto, > making it conditional. Ah, ok :) > > > The code after "goto" is disturbing. It looks like spill code, but

Chris Lattner wrote: > > Thanks, this works! I don't yet understand why spill code is needed there > > at all, but I'll return to that when I have branches working correctly. > > I'm not sure either. Can you send the code before and after register > allocation? Attached. > You might also try -regalloc=linearscan, as the default > allocator is, uhhh,

Chris Lattner wrote: > On Tue, 8 Jun 2004, Vladimir Prus wrote: > > While adding support for branch instructions in my backend, I run into a > > trouble. The code to handle branches looks like: > > The machine code after instruction selection is: > > > > entry (0x8681458): > > %reg1024 = load <fi#-1> > > %reg1025 = load

On Wed, 9 Jun 2004, Vladimir Prus wrote: > Chris Lattner wrote: > > > Thanks, this works! I don't yet understand why spill code is needed there > > > at all, but I'll return to that when I have branches working correctly. > > > > I'm not sure either. Can you send the code before and after register > > allocation? > > Attached. Okay, yeah

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 ?? -- 祝好！ 甄凯

Chris Lattner wrote: > > > I'm not sure either. Can you send the code before and after register > > > allocation? > > > > Attached. > > Okay, yeah the spill code looks right. The local allocator can't keep > virtual registers in physical registers across basic blocks. As such, the > vregs are spilled at the end of the entry block and then

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

Dear all, I'm new to the LLVM world and I'm trying to run reproduce the hello world example described here http://llvm.org/releases/3.8.1/docs/WritingAnLLVMPass.html. I started with a fresh new llvm-3.8.1 installation based on cmake (running on Linux x86) using the following command: cmake -DCMAKE_INSTALL_PREFIX=/path/to/llvm -DLLVM_TARGETS_TO_BUILD="X86" ../ The build

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

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

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

> opt -load lib­dum­my­pass.so -dum­my­pass hel­lo.ll Looks like you are loading a shared library different from "LLVMHello.so". did you change the name of the compilation unit from "Hello.cpp" into "dummypass.cpp"? (As asked previously by Andrzej) did you register the dummy pass? > RegisterPass<DummyPass> X("dummypass",