similar to: Problems building LLVMHello, spaces in path

Hi, I am trying to learn LLVM by following this article http://llvm.org/docs/WritingAnLLVMPass.html I checked 2.8 version from svn, built it and now I am trying to run Hello world example as $ opt -load ./Release/lib/LLVMHello.so -analyze but unfortunately it fails: Error opening './Release/lib/LLVMHello.so': ./Release/lib/LLVMHello.so: undefined symbol:

Hi all, I find all my passes are all broken with LLVM 3.4. Then I tried out the LLVMHello.so specified in the LLVM doc, http://llvm.org/docs/WritingAnLLVMPass.html and it also crashes. It seems all the functions in the pass do work, but LLVM crashes in the doFinalization() step. Does anyone know this problem? Thanks! Tianyin

Oh, you mean opt -disable-verify? Yes, it does eliminate the crashing... Do you know what's the problem, Eric? Thanks a lot! ~t On Tue, Aug 12, 2014 at 12:42 AM, Eric Christopher <echristo at gmail.com> wrote: > Tried opt -verify on your module? > > -eric > > On Tue, Aug 12, 2014 at 12:28 AM, Tianyin Xu <tixu at cs.ucsd.edu> wrote: > > Hi all, > >

I just follow the tutorial: http://llvm.org/docs/WritingAnLLVMPass.html Actually it's not only my module, I used the LLVMHello.so (a sample module in the source tree) and get the crash (I didn't do anything :-P). ~t On Tue, Aug 12, 2014 at 12:57 AM, Eric Christopher <echristo at gmail.com> wrote: > Weird, it definitely shouldn't be crashing. How did you create your

no... I guess verifier runs by default and it points to the doFinailization() function :-( ~t On Tue, Aug 12, 2014 at 12:53 AM, Eric Christopher <echristo at gmail.com> wrote: > No idea, I was suggesting to just run the verifier to see if it would > pinpoint what's broken about the module. > > -eric > > On Tue, Aug 12, 2014 at 12:52 AM, Tianyin Xu <tixu at

The module is shipped with the source code, so it's from the developers (not me). The path in the source tree is: llvm-3.4.2.src/lib/Transforms/Hello After compiled LLVM *#./configure --prefix=XXX --with-binutils-include=/path-to-binutils-2.24/include --enable-debug-symbols --enable-debug-runtime --enable-assertions --disable-optimized; make; make install* LLVMHello.so is generated at

I've built LLVM/Clang from svn under Cygwin on Windows 7. I'd like to build on the LLVMHello pass example, however, when I try: $ cd $LLVM/lib/Transforms/Hello $ make I receive a large number of errors which start with: llvm[0]: Linking Debug+Asserts Loadable Module LLVMHello.dll /cygdrive/c/Users/Graham/home/projects/llvm_cygwin/lib/Transforms/Hello/Debug+Asserts/Hello.o: In function

When I build LLVM, the message LLVMHello ignored -- Loadable modules not supported on this platform is shown and the LLVM Hello pass doesn't work. I am using Windows. Is this correct? LLVM Hello pass works only on Linux? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, everybody! On win32(s), lib/Transforms/Hello cannot be built cleanly. It will be built after 1st build. Linking the plugin LLVMHello.dll requires other libraries, especially LLVM.dll. May I move Hello to other location? Or, may I tweak llvm/Makefile? ...Takumi

For a while now I have noticed that when I build LLVM using CMake on my OS X machine there are two dynamically linked libraries, BugpointPasses and LLVMHello, that are built with the extension ".so" instead of the extension ".dylib". This has been causing four test cases to fail when running "make check". The attached patch modifies add_llvm_loadable_module in the

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

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

Björn, Can you try adding -fno-integrated-cc1 to the command-line, see if you get more infos? De : cfe-dev <cfe-dev-bounces at lists.llvm.org> De la part de Eric Astor via cfe-dev Envoyé : November 11, 2020 8:39 AM À : Gaier, Bjoern <Bjoern.Gaier at horiba.com> Cc : Clang Dev <cfe-dev at lists.llvm.org> Objet : Re: [cfe-dev] Running LLVMHello Pass from Clang(-cl) The

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.

Hi! I'm trying to build a fast Clang for myself to use for debug builds on Clang itself, but I've been struggling for a very long time on it. Could you please help? I've been following this guide: https://llvm.org/docs/HowToBuildWithPGO.html I've quickly learned that its outdated, because the script it talks about doesn't work with the monorepo layout at all, but in any

Graham, good morning. To build LLVMHello on cygming, you should configure llvm with --enable-shared . Even with enable-shared, you might build lib/Transforms/Hello manually. (yeah, on cygming, LLVMHello should depend on tools/llvm-shlib) And, you'd be better to build with --enable-optimized. With enable-shared, llvm-shlib tends to fail with too many debug symbols. HTH, ...Takumi

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

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

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:

Hi all I am trying hello pass in llvm. I have compiled and could generate LLVMHello.so but while giving the pass using opt i am getting below mentioned error. Command used: *opt-2.8 -load ../../cse231_project/llvm/llvm-2.9/Debug/lib/LLVMHello.so -hello < hello.bc* Error opening '../../cse231_project/llvm/llvm-2.9/Debug/lib/LLVMHello.so':