similar to: [LLVMdev] Hello Pass Problem

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Hello Pass Problem"

2011 Oct 14
3
[LLVMdev] undefined symbol: _ZN4llvm12PassRegistry12registerPassERKNS_8PassInfoEb
Has anyone seen this error before? I'm trying to load a pass that apparently isn't registered, it's just the "Hello World" sample , so I don't see the problem. Error: me at here:~/llvm/llvm_core/llvm-2.9$ opt -load Release/lib/LLVMHello.so -hello <cdfg.c> /dev/null Error opening 'Release/lib/LLVMHello.so': Release/lib/LLVMHello.so: undefined symbol:
2011 May 03
3
[LLVMdev] Loop-Unroll optimization
Hi, You might want to try running -loops -loop-simplify before loop unroll. >From loop simplify.cpp This pass performs several transformations to transform natural loops into a00011 // simpler form, which makes subsequent analyses and transformations simpler and00012 // more effective. Arushi On Tue, May 3, 2011 at 2:17 PM, Manish Gupta <mgupta.iitr at gmail.com> wrote: > You
2011 May 03
2
[LLVMdev] Loop-Unroll optimization
Hi, you need to run some optimization passes first. (like -O2) 2011/5/3 Manish Gupta <mgupta.iitr at gmail.com> > I just want to try loop-unroll and see corresponding changes in the bitcode > file. For that any loop will do. Have you been able to test llvm loop-unroll > successfully? > > > On Mon, May 2, 2011 at 10:04 PM, Yuan Pengfei <coolypf at qq.com> wrote: >
2011 May 03
0
[LLVMdev] Loop-Unroll optimization
Even after all the sequence of commands below bit-code is not showing any effect of loop-unrolling *manish at manish:~/Test2$ llvm-gcc-4.2 -O2 -emit-llvm Hello.c -c -o Hello.bc* *manish at manish:~/Test2$ opt-2.8 -loops Hello.bc -o Hello1.bc* *manish at manish:~/Test2$ opt-2.8 -loopsimplify Hello1.bc -o Hello2.bc* *manish at manish:~/Test2$ opt-2.8 -indvars Hello2.bc -o Hello3.bc* *manish at
2011 May 04
1
[LLVMdev] Loop-Unroll optimization
1. You should run the passes in the same opt command, for passes like loops which is an analysis pass provides results to the following passes. 2. You can pass a -debug flag to opt to see the some debugging info. 3. I tried this opt -mem2reg -loops -loopsimplify -loop-unroll -unroll-count=3 -debug loop.o -o tt.bc and got this message. Loop Size = 14 Can't unroll; loop not terminated by
2011 May 03
0
[LLVMdev] Loop-Unroll optimization
You mean like *llvm-gcc-4.2 -O2 -emit-llvm Hello.c -c -o Hello.bc* But still i am not able to observe any effect on bit code by running *opt-2.8 -loop-unroll Hello.bc -o Hello_unroll.bc* On Tue, May 3, 2011 at 3:58 AM, Zakk <zakk0610 at gmail.com> wrote: > Hi, you need to run some optimization passes first. (like -O2) > > 2011/5/3 Manish Gupta <mgupta.iitr at gmail.com>
2011 May 03
2
[LLVMdev] Loop-Unroll optimization
Hi, > The loop that I am trying it on is: > for(i=0; i< 1000; i++) > { > c[i] = a[i] + b[i]; > } I can't find any benefit unrolling this loop. ------------------ Yuan Pengfei Peking Unversity, China
2011 May 03
0
[LLVMdev] Loop-Unroll optimization
I just want to try loop-unroll and see corresponding changes in the bitcode file. For that any loop will do. Have you been able to test llvm loop-unroll successfully? On Mon, May 2, 2011 at 10:04 PM, Yuan Pengfei <coolypf at qq.com> wrote: > Hi, > > > The loop that I am trying it on is: > > for(i=0; i< 1000; i++) > > { > > c[i] = a[i] + b[i]; > > }
2007 Apr 13
2
[LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile
And this brings back CommandLine Error: Arugment blah defined more than once! And without this, opt -load .../LLVMHello.dylib -hello does not work on Darwin because dyld is not able to find SlowerOperationInformer ;) thoughts ? - Devang On Apr 13, 2007, at 11:28 AM, Devang Patel wrote: > > > Changes in directory llvm/lib/Transforms/Hello: > > Makefile updated: 1.7 ->
2006 Feb 08
1
[LLVMdev] LLVM Hello Project generating .lo file in place of .so file.
Hello, I am trying to compile the Hello Project of the lib/Transforms/Hello subdirectory according to the instructions given on http://llvm.cs.uiuc.edu/docs/WritingAnLLVMPass.html document. I am using 1.6cvs source to compile LLVM. The problem is that after running the Make file on the project, the Debug subdirectory contains .lo file in place of .so file. I need the .so file to use with opt
2007 Apr 13
0
[LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile
On Fri, 13 Apr 2007, Devang Patel wrote: > And this brings back CommandLine Error: Arugment blah defined more > than once! > > And without this, opt -load .../LLVMHello.dylib -hello does not work > on Darwin because dyld is not able to find SlowerOperationInformer ;) I think libhello should drop its use of SlowOperationInformer. -Chris > On Apr 13, 2007, at 11:28 AM, Devang
2006 Aug 28
2
[LLVMdev] opt -load error on Darwin
Hi, I am following the instructions on Writing an LLVM Pass on Darwin(8.7.0) powerpc. The loadable library is built. But "opt -load " gives error saying "Symbol not found". I am using LLVM 1.8. Could someone tell me how to fix it? I have tried the same procedure on Pentium4 Redhat9. Everything is ok there. So I think there must be some specific problem on Darwin that I should
2006 Aug 28
0
[LLVMdev] opt -load error on Darwin
On Sun, 2006-08-27 at 21:57 -0500, Jing Yu wrote: > Hi, > Hi Jing, > I am following the instructions on Writing an LLVM Pass on > Darwin(8.7.0) powerpc. The loadable library is built. But "opt -load > " gives error saying "Symbol not found". I am using LLVM 1.8. Could > someone tell me how to fix it? I have tried the same procedure on > Pentium4 Redhat9.
2009 Oct 12
1
[LLVMdev] current state of building analysis passes out-of-tree with llvm-config?
Hi, what's the current state of being able to build simple analysis passes out-of-tree against only llvm headers and libraries with llvm-config? I see that clang and klee do not use llvm-config but for example rubinius does. Should both approaches be documented? Currently for example docs/WritingAnLLVMPass.html says "you need to create a new directory somewhere in the LLVM source
2015 Sep 17
2
Problems building LLVMHello, spaces in path
I recently had a problem creating LLVMHello. I used this CMake file #!/bin/sh # clangcmake.sh cmake -G "Eclipse CDT4 - Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_ECLIPSE_VERSION=4.5 -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang ../llvm then I ran make LLVMHello and the build failed
2006 Aug 28
3
[LLVMdev] opt -load error on Darwin
Thank you, Reid. I have applied tha patch to ltdl.c ltdl.h. The problem still exists. I looked up the symbol on libLLVMCore.a, and found three U-entries and one T-entry. However, the Darwin linker is not able to find the T-entry. Any idea? pollux:~/test jingyu$ opt -load /Users/jingyu/tools/build-ppc/Release/lib/LLVMHello.so -help Error opening
2008 Oct 22
2
[LLVMdev] Regarding Error on Mac OSX
Hello guys, I get the following error whenever i try to check if the following pass exists. I am using Mac OSX leopard and gcc4 opt -load ../Release/lib/LLVMHello.dylib -hello Error opening '../Release/lib/LLVMHello.dylib': dlopen(../Release/lib/LLVMHello.dylib, 1): Symbol not found: __ZN4llvm12FunctionPass11runOnModuleERNS_6ModuleE Referenced from:
2010 Oct 07
0
[LLVMdev] Hello pass?
Owen, I have an issue about the Hello on windows. Please seek "RFC: change build order (or location) of LLVMHello plugin" in this list, thank you :) My proposal: move it onto a new directory plugins/ ps. I would like to know why the Hello plugin is on lib/Transforms. Is it a historical reason? ...Takumi 2010/10/7 Owen Anderson <resistor at mac.com>: > Hey, > > Does
2013 Feb 11
2
[LLVMdev] llvm pass
hello sir, i build llvm-clang successfully in my pc but while running a pass i am geetting this error praveen at ubuntu:~/Desktop/LLVM/ build/Release$ opt -load /lib/LLVMHello.so --help Error opening '/lib/LLVMHello.so': /lib/LLVMHello.so: cannot open shared object file: No such file or directory -load request ignored. please help me to overcome the error. -------------- next part
2008 Oct 23
0
[LLVMdev] Regarding Error on Mac OSX
Hi, There is reported bug about this (#2771), or at least related. http://llvm.org/bugs/show_bug.cgi?id=2771 Though it seems there is no "proper" solution known so far. The workaround is to use 'opt' from the Release/bin directory In your case: ../Release/bin/opt -load ../Release/lib/LLVMHello.dylib -hello Would probably work. Best regards Vlado > Hello guys, > >