similar to: [LLVMdev] 'Implementing a language with LLVM' tutorial

On 11/5/07, Chris Lattner <clattner at apple.com> wrote: > Hi All, Hi, > > http://llvm.org/docs/tutorial/ Very interesting tutorial, reading it now :) > Anyone have thoughts or feedback? :) There's a typo in http://llvm.org/docs/tutorial/LangImpl5.html "the Phi node expects to have an extry" s/extry/entry/ Best regards, Edwin

On Mon, 5 Nov 2007, Vikram S. Adve wrote: > -- It would be helpful to add some navigation links at the top and bottom of > the pages. I added a TOC to each chapter, thanks. > -- Not clear why PrototypeAST::Codegen returns a Function* instead of a > Value* like the other CodeGen methods? I clarified this in the text. The short version is that PrototypeAST doesn't correspond

I am new to llvm so I might be missing a critical step. My system is Fedora 12 but this also happens in Mac OS X 10.6.2. Here are the steps I used to compile llvm: export TARGETS=x86,x86_64,cpp export INSTALLDIR=/home/rovitotv/llvm ../llvm-2.6/configure --prefix=$INSTALLDIR --enable-bindings=none --enable-targets=$TARGETS --enable-optimized --with-llvmgccdir=$INSTALLDIR

Thank you for this reply. If so, is there any way to merge basic blocks into a single one? Thanks, Seung J. Lee ---- Original message ---- >Date: Fri, 29 Jun 2007 22:27:38 +0200 >From: Basile STARYNKEVITCH <basile at starynkevitch.net> >Subject: Re: [LLVMdev] LLVM assembly without basic block >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Seung

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

Hello All Does any know about some opensource multithread-compatible (or concurrent) garbage collector library, if possible suitable for LLVM? (I mean that I want several mutator threads; the collector can be stoptheworld or concurrent ....) H.Boehm's conservative GC is multithread compatible, but seems quite slow (allocation is about the time of a C malloc). And it is well known that

https://bugs.freedesktop.org/show_bug.cgi?id=51144 Bug #: 51144 Summary: significant pixel corruption in text Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

The release branch has been created and the llvm-gcc mirror updated (thanks Bill!). I will be doing some preliminary testing before I request the help of the community to test the release. During this time, I ask that developers only commit documentation changes to the release branch and email the list with any bug fixes that need to be merged into the release branch. Bug fixes have to be

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

Chris Lattner wrote: > On Mon, 5 Nov 2007, Vikram S. Adve wrote: >> -- It would be helpful to add some navigation links at the top and bottom of >> the pages. > > I added a TOC to each chapter, thanks. May I also suggest adding to each HTML page a link to the topmost http://llvm.org/docs/tutorial/ -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email:

Hello All, What version of g++ is usable to compile the latest LLVM CVS snapshot on a Linux/x86-64 (AMD64) Debian/ Sid or Etch plateform? What compiler do LLVM dzevelopers use to compile LLVM on Linux/X86-64 systems? IKt seems that most versions of g++ fail to compile LLVM and that some others compile it wrongly (producing buggy code)? Why can't g++-4.1 be used? FWIW, the latest gcc

Le Tue, May 08, 2007 at 10:17:41PM -0700, Tanya M. Lattner écrivait/wrote: > > Here is the schedule: > > May 7th - Release branch created. Developers should begin reviewing > all documentation. > > May 14th - Tar balls and binaries are released for general testing. I'll > also need volunteers to create additional llvm-gcc binaries that I have > not provided.

Hello All, On a Debian/AMD64 host I am surprised that there is apparently no way to generate position independent code in shared object (i.e. to output files which are easy dlopen-able without pain)? I probably missed something obvious, but what? I want to compile LLVM assembly source code -suitably generated- into .so as directly as possible... Regards -- Basile STARYNKEVITCH

Hey Chris: Here are the diffs for the next few chapters of the tutorial that I have edited. Please note that there is one recurring fix (straight-forward is changed to straightforward). Once again, these are simple changes, not including any real content changes. Thanks, K.Wilson On Sun, 2007-11-04 at 23:14 -0800, Chris Lattner wrote: > Hi All, > > LLVM has long needed a tutorial for

Hello List, (apparently this list is moderated) Le/On Sun, Nov 07, 2004 at 03:45:41PM -0600, Misha Brukman écrivait/wrote: > On Sun, Nov 07, 2004 at 10:33:09PM +0100, Basile STARYNKEVITCH > wrote: Basile>> I want to try to use LLVM only for JIT only use (generating code in Basile>> memory for x86 and, when available PowerPC [32bits]) If you want to know I am experimenting

Dear All, I downloaded the latest CVS of llvm I want to try to use LLVM only for JIT only use (generating code in memory for x86 and, when available PowerPC [32bits]) How do I ./configure to avoid being asked about llvmgcc, which, in my very partial understanding, is only used to parse C code... If I understand correctly what Chris Lattner emailed me, LLVM uses only GCC frontend for C & C++

Hi Guys, I am really a fresh man on compiler. I want to make a compiler that transform C-like language into assemble form, as the the same as Pixie's or Aqsis's RenderMan Shading Language compiler, just like this, #!version 2.1.1 surface #!parameters: uniform float Ka = 1 uniform float Kd = 1 #!variables: varying vector Nf varying vector temporary_0 varying vector temporary_1 varying

Le Thu, May 03, 2007 at 09:36:22AM -0700, Chris Lattner écrivait/wrote: > On Thu, 3 May 2007, Basile STARYNKEVITCH wrote: > > > > > FWIW, the latest gcc snapshot from yesterday gcc version 4.3.0 20070501 > > (experimental) fail to compile latest LLVM (with compile errors!). > > Please file an llvm bug report with these errors. It may be that we are > doing

Hello (my machine is a Debian/Sid/x86-64/Core2) Assuming I have one C source file chello.c, to compile it into a dynamically loadable thru dlopen shared object, I can run gcc -fPIC -shared -O chello.c -o chello.so I thought that, assuming I have one llvm source ehello.ll, the equivalent would be llvmc2 -opt ehello.ll -o ehello.so but it is not that simple. Any clues ? May I also

Hello, with the latest LLVM (almost 2.0 CVS) what is the right way to read a module from a byte array fetched from a database? I thought that I could subclass llbm::module to add my own fields (typically, a MySQL id number) and then parse it as bitcode, but I am stuck, since apparently the only way to parse bitcode is to use a BitcodeReader then calling materializeModule gives a fresh llvm