similar to: [LLVMdev] LLVMHello pass compile error under Cygwin

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

Thankyou Takumi, Without --enable-optimized I get a"File too big" error from the linker: ... llvm[1]: Linking all LLVMLibs together for LLVM-3.0svn /usr/lib/gcc/i686-pc-cygwin/4.5.3/../../../../i686-pc-cygwin/bin/ld: /cygdrive/c/Users/Graham/home/projects/llvm_cygwin3/tools/llvm-shlib/Debug+Asserts/LLVM-3.0svn.a.o: too many sections (59747)

Good evening, Michael. 2010/9/5 Michael Spencer <bigcheesegs at gmail.com>: > Do you know what the exact problem is? It would be best to fix the > Makefile instead of moving it. And sense it is a transformation, the > build system is broken if you _have_ to move it. I am sorry, I don't understand what *the exact problem" is. I can describe facts; - Hello is the only

Hello! At first, i want to run the latest HandBrake (version 0.93) on a Mac with Mac OS 10.4 (Tiger). The problem is, that Handbrake is developed for Mac OS 10.5 (XCode SDK is not compatible to Mac OS 10.4 one). So i decided to try it with wine/darwine. Because wine is better supported on Linux and you can get easier newer version (apt-get), i decided to run HandBrakeCLI.exe on Debian Etch

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

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:

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

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

Hello, I'm starting to play with LLVM today and I've trouble compiling it. I'm working under Windows Vista, with the gcc from Cygwin: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Is LLVM supposed to work with this version of GCC (probably using the -mno-cygwin option to get a Mingw-like behavior)? The LLVM source tree is from the current SVN trunk. Compilation

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

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

On Sat, Sep 4, 2010 at 9:53 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > 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? > >

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:

On Tue, 19 Sep 2006, Anton Vayvod wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x00634572 in (anonymous namespace)::X86DAGToDAGISel::DeleteNode ( > this=0x4c3b710, N=0x4c3e5c0) > at /llvm/obj/lib/Target/X86/X86GenDAGISel.inc:77 > 77 SDNode *Operand = I->Val; > > SEGFAULT seems to come before register allocation pass is being run. Are you

> Are you using LLVM CVS? If not, please update. Yes, I'm using LLVM CVS. Updated a couple of hours ago. If so, please run 'make > bugpoint-llc' in that directory and file a bug. This is an instruction > selector bug, not yours. We'll be happy to fix it if it's not already > fixed in LLVM CVS. The test is running and I already have Segmentation Fault

Graham, please try "--disable-embed-stdcxx". In TOT, "--enable-embed-stdcxx" by default. It would be the time to change the default.... ...Takumi