similar to: [LLVMdev] Kaleidoscope toy4 failure seg fault on llvm::ExecutionEngine::getTargetData (this=0x0)

First, you have to call llvm-g++ to use the llvm-gcc front end, but it doesn't matter here. I'd like to suggest that you use pastebin to put your code and the send us the link, so that we can download it. The problem is that TheExecutionEngine is set to NULL (maybe because of a previous error), but it will be really better if you use pastebin. On Wed, Feb 17, 2010 at 6:01 AM, Todd Rovito

On Wed, Feb 17, 2010 at 6:29 AM, Conrado Miranda <miranda.conrado at gmail.com> wrote: > First, you have to call llvm-g++ to use the llvm-gcc front end, but it > doesn't matter here. I got the compile command from the Kaleidoscope documentation. > I'd like to suggest that you use pastebin to put your code and the send us > the link, so that we can download it. The

Hello all, When extending the tutorial to support global variables I'm getting the following linker error: glob.o:glob.cpp:(.text+0x12241): undefined reference to `vtable for GlobalExprAST' collect2: ld returned 1 exit status GlobalExprAST class is: /// GlobalExprAST - Expression class for globals class GlobalExprAST : public ExprAST { std::string Name; ExprAST *Init; public:

Greetings, I am having trouble getting the Kaleidoscope example to build from tutorial #3 on Mac OS X 10.6.2. I didn't have too much trouble getting llvm-2.6 and llvm-gcc-frontend to build. Thanks for the help. Here are the steps I followed: Environment variables for build export LLVMOBJDIR=/opt/llvm export TARGETOPTIONS='--with-arch=nocona --with-tune=generic' export

Hello, I get a crash in my program that uses exceptions and the LLVM JIT, even though the exceptions are controlled and thrown/catched in a part that doesn't deal with LLVM. I noticed that llvm-config --cxxflags includes the -fno-exceptions flag. Do I need to throw no exceptions whatsoever in my application to use LLVM JIT? As a minimal example, I modified the code in

On Mon, 5 Nov 2007, Aaron Gray wrote: >> Anyone have thoughts or feedback? :) > > Nice job. The only bit that is not immediately clear is the 'Proto' > variable, but is clear when looking through the code at the end of the page. Where in the tutorial? What would you suggest that I say? > Could do with a link to the LLVMBuilder class reference material. I added a link

There were some typos in the tutorial. This patch should fix them: index b7f968b..50619e0 100644 --- a/docs/tutorial/LangImpl2.html +++ b/docs/tutorial/LangImpl2.html @@ -933,7 +933,7 @@ public: /// of arguments the function takes). class PrototypeAST { std::string Name; - std::vector&lt; Args; + std::vector&lt;std::string&gt; Args; public: PrototypeAST(const std::string

Hi all, I've started work on a new programming language for which I am considering using LLVM as the backend, and trying to experiment with it using the Kaleidoscope demo compiler. Taking the full source listing from http://llvm.org/docs/tutorial/LangImpl3.html#code and trying to compile it with the provided instructions gives me the following errors: a at a-desktop:~$ g++ -g -O3 toy.cpp

Probably you missed to install llvm-dev package with headers for llvm. 2010/1/4 Russell Wallace <russell.wallace at gmail.com> > Hi all, > > I've started work on a new programming language for which I am > considering using LLVM as the backend, and trying to experiment with > it using the Kaleidoscope demo compiler. > > Taking the full source listing from >

Hi, I'm incrementing my toy compiler to account for variable mutations around if/else blocks. Reading the Kaleidoscope tutorial, I've learnt that I can substitute the PHI node creation by allocas and retrieving the value later, if needed. The Kaleidoscope example seems to account for one value only, the result of: Value *ThenV = Then->Codegen(); (...) Value *ElseV =

Hi, Try these scripts to build llvm and llvm-gcc. It's the ones I use and I managed to get them to work when I saw another build script using those CFLAGS. They compile llvm and stuff using only x86_64, but you can then generate code for i386 (just use a different backend). The configuration options are at the top of the scripts and they install llvm and llvm-gcc to ~/llvm. Regards,

Very nice. Here's a couple comments on the first 6 chapters: http://llvm.org/docs/tutorial/LangImpl1.html "We handle comments by skipping to the end of the line and then returning the next comment." Shouldn't this say "returning the next comment"? http://llvm.org/docs/tutorial/LangImpl2.html I was a bit confused at first because the AST node classes are called ASTs.

Hi all, from llvm-trunk I'm getting this failure: llvm[0]: Running test suite make[1]: Entering directory `/home/rleissa/projects/llvm/build_debug/test' Making a new site.exp file... Making LLVM 'lit.site.cfg' file... Making LLVM unittest 'lit.site.cfg' file... make -C /home/rleissa/projects/llvm/build_debug/test/../tools/clang/test lit.site.cfg Unit/lit.site.cfg

Hello All I 'm studing LLVM/Clang and trying to follow the Kaleidoscope tutorial (Release 2.6 version). I found some minir docu-bugs and added them to Bugzilla. However, Now I found a show-stopper for me, the toy (v4) demo does build, but does crash, on any input. Even a simpe ';'! Looking into the (demo-code) found the that the JIT can't be build/ created,/loaded/... Which

> On Mon, 5 Nov 2007, Aaron Gray wrote: >> Nice job. The only bit that is not immediately clear is the 'Proto' >> variable, but is clear when looking through the code at the end of the >> page. > > Where in the tutorial? What would you suggest that I say? First reference in 'Function *FunctionAST::Codegen()'. What Proto is is not totally clear till

I'm working through the Kaleidoscope tutorial through section 2.4, and I've encountered some problems: several minor bugs, and finally a bus error that has me stumped: ------- In the code listed in LLVM Tutorial section 2.2 Implementing a Parser and AST. Line 19 has a comma at the end of line that shouldn't be there Line 120 is missing a closing angle bracket. Line 120 should be

Nice work, Chris! This is a much needed tutorial. Some comments: -- It would be helpful to add some navigation links at the top and bottom of the pages. -- Not clear why PrototypeAST::Codegen returns a Function* instead of a Value* like the other CodeGen methods? -- It can be convenient to use Visitor methods on the AST classes for code generation, instead of hard-coding the CodeGen

On Thu, Oct 1, 2009 at 4:35 PM, Renato Golin <rengolin at systemcall.org> wrote: > Hi, > > I'm incrementing my toy compiler to account for variable mutations > around if/else blocks. > > Reading the Kaleidoscope tutorial, I've learnt that I can substitute > the PHI node creation by allocas and retrieving the value later, if > needed. The Kaleidoscope example

Hello , I have build llvm from release_38 branch ( only llvm and clang ) and install it. My DYLD_LIBRARY_PATH points to installation-directory/lib. I am compiling example files for Kaleidoscope with following command : clang++ -g toy.cpp -std=c++11 `llvm-config --cxxflags --ldflags --system-libs --libs core mcjit native` -O3 -o toy but it fails with following error: Undefined symbols for

Good Day! I have a problem with rendering of cyrillic font in one window. Everything is fine in others windows of the same program. I've tried to copy fonts from Windows, where this program works, but it doesn't help. LANG=ru_RU.UTF-8 I runned wine with "WINEDEBUG=trace+font,trace+dialog": ... trace:font:CreateFontIndirectW (-21 0 0 0 31 3 2 1 204) L"Courier New" Bold ?