similar to: [LLVMdev] Is there a guide to LLVM's components?

I constructed an LLVM 2.7 VS solution with cmake, but it has 66 projects: ALL_BUILD, ".\ALL_BUILD.vcproj" BrainF, "examples\BrainF\BrainF.vcproj" Fibonacci, "examples\Fibonacci\Fibonacci.vcproj" FileCheck, "utils\FileCheck\FileCheck.vcproj" HowToUseJIT,

David Piepgrass <dpiepgrass at mentoreng.com> writes: > One thing that helps me understand complex software is a dependency > graph. I found an LLVM dependency graph at > > https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies > > but it's really messy and hard to follow. From that graph I made a > cleaner graph by hand

> > I found an LLVM dependency graph at > > > > https://llvm.org/svn/llvm- > project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies > > > > but it's really messy and hard to follow. From that graph I made a > > cleaner graph by hand (attached)... sorry about the fax-quality > > scan. But I have some questions about it... > > >

Does not seem to be a straight error with LLVM itself, but rather the tools, linking issues, here are the errors: Opt: 30> Creating library R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.lib and object R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.exp 30>LLVMScalarOpts.lib(IndVarSimplify.obj) : error LNK2019: unresolved external symbol "public: bool __thiscall

Where exactly is this mythical Kaleidoscope example? I have llvm 2.5 installed. examples dsw$ ls BrainF Fibonacci Makefile ParallelJIT CMakeLists.txt HowToUseJIT ModuleMaker > Date: Sat, 3 Oct 2009 21:40:44 +0100 > From: Renato Golin <rengolin at systemcall.org> > Subject: Re: [LLVMdev] LLVM-Kaleidoscope tutorial > > 2009/10/3 Remy Demarest <remy.demarest at

Hello, I downloaded LLVM 2.6 and was attempting to compile it with TDM-GCC 4.4.1-tdm2-sjlj + cmake 2.6.4 and this happened: =============Console=================== C:\projects\game-editor\LLVM\build-root>mingw32-make [ 2%] Built target LLVMSystem [ 5%] Built target LLVMSupport [ 7%] Built target tblgen [ 7%] Built target intrinsics_gen [ 10%] Built target LLVMCore [ 12%] Built target

Hi, While building svn using CMake on an Ubuntu 9.04 system (gcc 4.3.3, binutils 2.19.1, 32-bit kernel and libs): Linking CXX executable ../../bin/llvm-dis [ 93%] Built target llvm-dis Scanning dependencies of target llc [ 93%] Building CXX object tools/llc/CMakeFiles/llc.dir/llc.cpp.o Linking CXX executable ../../bin/llc /usr/bin/ld: error in ../../lib/./LLVMX86AsmPrinter.o(.eh_frame); no

I'm currently looking at how to use llvm as a backend for compiling executable programs; here's my understanding of the state of affairs so far: Kaleidoscope demonstrates how to generate code in memory, and run it in memory using JIT for interactive use (which will be handy in due course for providing an interactive option); BrainF demonstrates how to output intermediate code; but it is

Hi all, here comes the patch for the first wave of Use class size reduction. I have split it into 3 files, corresponding to - header changes - implementation changes - applications This at the moment does not contain the description how the size of the Use class will be reduced from 16 to 12 bytes, I am going to send that in a separate patch. This wave primarily consists of changes that are

I am considering using LLVM in a project for a Windows CE where space is at a premium. My jaw dropped when I checked the size of HowToUseJIT.exe (VC++ Win32 debug): 15.4 MB! The release build of HowToUseJIT is "only" 3.39 MB, but this is still 85% larger than the binary to which I was thinking of adding LLVM. The top ten LLVM libraries (Win32 *.lib) are pretty huge: Release Bld Debug

Hi all, I downloaded LLVM to play with today and found that the BrainF example compiler fails with an assertion error like so: examples$ ./BrainF -jit /tmp/test.bf BrainF: Instructions.cpp:242: void llvm::CallInst::init(llvm::Value*, llvm::Value* const*, unsigned int): Assertion `(NumParams == FTy->getNumParams() || (FTy->isVarArg() && NumParams > FTy->getNumParams()))

I don't suppose anyone knows what (or how to find out what) the actual command to compile Kaleidoscope is? I followed cmake/nmake down through maybe half a dozen levels before getting lost, so I tried to develop a compiler invocation from scratch. I got as far as cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp which successfully generated toy.obj and spat out 86 link time

Russell Wallace <russell.wallace at gmail.com> writes: > I don't suppose anyone knows what (or how to find out what) the actual > command to compile Kaleidoscope is? I followed cmake/nmake down > through maybe half a dozen levels before getting lost, so I tried to > develop a compiler invocation from scratch. I got as far as > > cl /EHsc /I\d\llvm-2.6\include

> > What's wrong with running LLVM on ARM? > > LLVM can generate code for ARM, but the JIT requires extra target and > platform dependent stuff, and that's not done for arm-wince. The release notes say "compiler_rt now supports ARM targets". What else is needed? Keep in mind that I do not need (or want) Clang or any of the optimizers: I just want to generate

> > I just moved to the CMake solution. By the way, the generated libs > > haven't the same names. > > Which ones? The only difference is that we now generate .lib files > where > .obj were generated on the past, and require a parameter to be passed > to > the linker for including them on the final executable. I was linking with VMCore.lib support.lib

Thanks to OvermindDL1 for pointing this out: compiling with Visual C++ actually works! Basically it's just a matter of running cmake (default settings are fine) then nmake, and I've got what appears to be a working version of LLVM. Kaleidoscope crashes on attempting to exit with ^Z: C:\llvm\bin>Kaleidoscope.exe ready> 1+2; ready> Evaluated to 3.000000 ready> 3*4; ready>

Morten, I've applied these patches. Thanks for the updates! Reid. On Mon, 2004-11-15 at 01:26, Morten Ofstad wrote: > Hi, > > when I updated the sources today there were several small problems that > stopped the windows version from compiling, here are the patches > > m. > > > ______________________________________________________________________ > Index:

Hi Dmitri, For what version of VS did you update the project files? Ted On May 17, 2008, at 3:00 PM, Dmitri Makarov wrote: > attached is the diff of vcprojs that need to be changed to fix the VS > build as of revision: 51224. > > I don't know if this catches all the missing bits, but this does build > all the way through. > > > Index: win32/Analysis/Analysis.vcproj

On Sun, Nov 07, 2004 at 11:40:58PM +0100, Basile STARYNKEVITCH wrote: > I did "make" inside llvm/examples/ and inside > llvm/examples/HowToUseJIT/ and expected to get an ELF executable.. But > I've only got the 2 Release/HowToUseJIT.[do] files.. All executables are placed in tools/$(BUILD_TYPE), in your case, llvm/tools/Release. That is there from the time before we had

I'm trying to get the Kaleidoscope tutorial mini compiler working on Windows (as a trial run for developing a compiler using LLVM). Kaleidoscope uses the C++ linkage method of code generation (as opposed to spitting out intermediate code in a text or binary file), which as I understand it is the preferred way of doing it for a few reasons, one of them being that it gives you JIT capability,