similar to: [LLVMdev] Re: stacker doc

Hi, I'm new to LLVM, and I'm trying to get things set up. So far I've successfully gotten the C and C++ frontends to run, using the pre-compiled Mac OS X PPC binaries. I've also successfully compiled the main LLVM package (minus the gcc frontend). I'm now trying to get the Stacker sample project to compile. I checked out the Stacker directory from svn, and put it in my

LLVMers, I've hacked Brian's BitterMelon demo to include Stacker and bytecode analysis information. You can try it out on the mirror at: http://llvm.x10sys.com/demo/index.cgi A new language radio buttons below the text input area permits Stacker input to be compiled and there is an extra option for generating bc data with llvm-bcanalyzer. If you're new to LLVM, try pasting the

I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index:

Hi LLVM'ers, when configuring llvm on mingw32: /C/projects/src/llvm-1/llvm/configure --prefix=/C/MinGW/msys/home/Administrator/llvm --enable-targets=x86 I got this error: configure: configuring in projects/Stacker configure: running /bin/sh '/C/projects/src/llvm-1/llvm/projects/Stacker/configure' --prefix=/C/MinGW/msys/home/Administrator/llvm

If I remember correctly, you get the following warning when you configure LLVM: configure:2087: WARNING: Unknown project (Stacker) won't be configured automatically That leads would lead me to believe that you need to run configure inside llvm/projects/Stacker (and inside llvm/projects/Hello) before you run gmake inside of them. I don't know for sure, but perhaps that might fix

On Tue, Apr 8, 2008 at 8:00 PM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > On 2008-04-08, at 20:21, Lane Schwartz wrote: > > > I checked out the Stacker directory from svn, and put it in my llvm- > > src/projects directory. Unfortunately, when I run make, I get the > > errors below. I wondered whether the stacker code might simply be > > out of

Hello, I was wondering what happened to the "Stacker" example. The old link to it "http://llvm.org/docs/Stacker.html" is dead. Thanks, Wayne ________________ Wayne Anderson

I'm also getting these errors: gmake[2]: Entering directory `/usr/home/llvm/projects/Stacker' ../../Makefile.common:60: ../../Makefile.config: No such file or directory ../../Makefile.common:65: /Makefile.rules: No such file or directory gmake[2]: *** No rule to make target `/Makefile.rules'. Stop. gmake[2]: Leaving directory `/usr/home/llvm/projects/Stacker' Everything else

On 2008-04-08, at 20:21, Lane Schwartz wrote: > I checked out the Stacker directory from svn, and put it in my llvm- > src/projects directory. Unfortunately, when I run make, I get the > errors below. I wondered whether the stacker code might simply be > out of date It is. The fixes are likely mechanical, but just require someone stepping up and submitting a patch. — Gordon

Personally, I don't think LLVM projects should need much in the way of autoconf stuff. They certainly don't need to replicate things like install-sh and mkinstalldirs. I'd vote for taking these out of the projects rather than making the makefiles deal with them. I think in most cases these are just historical artifacts that have been with the projects since long before the new

While it is great that LLVM has an IR Verifier, its a little troublesome to use because it separates the point of detection from the source of the problem. That is, the verifier gets run on a module or function after its been built. By that point, the compiler's state has moved past the point at which the error was placed into the module or function. Trying to track down the source of the

Hi! In current LLVM CVS: llvm/projects/Stacker/Makefile.common.in llvm/projects/sample/Makefile.common.in llvm-java/llvm-java/Makefile.common.in have line: include $(LLVM_OBJ_ROOT)/Makefile.common that have line: include $(LLVM_OBJ_ROOT)/Makefile.config (also $(LLVM_OBJ_ROOT)/Makefile.config used in llvm-test/Makefile.config.in) and llvm/Makefile.config.in have lines: INSTALL_SH :=

Hi all! I have sucessfully installed LLVM 1.9 under FreeBSD on a x86 PC. I have successfully executed "An Example Using the LLVM Tool Chain" that is written in the document http://llvm.org/docs/GettingStarted.html When I tried out the demo projects "Hello" and "Stacker" I get compile errors. When I run "gmake" in the directory

As a learning aid for myself and for other would be source language writers for LLVM, I have decided to write a very simple language I'm calling "Stacker". Its kinda like Forth but way, way, way simpler. Its nowhere near ANS Forth and it won't be useful for much other than demonstrating how to create a source language using LLVM. I thought I'd mention this just so everyone

On Mon, 2005-02-14 at 20:53, Chris Lattner wrote: > On Mon, 14 Feb 2005, Reid Spencer wrote: > > > Personally, I don't think LLVM projects should need much in the way of > > autoconf stuff. They certainly don't need to replicate things like > > install-sh and mkinstalldirs. I'd vote for taking these out of the > > projects rather than making the makefiles

On Mon, 14 Feb 2005, Reid Spencer wrote: > Personally, I don't think LLVM projects should need much in the way of > autoconf stuff. They certainly don't need to replicate things like > install-sh and mkinstalldirs. I'd vote for taking these out of the > projects rather than making the makefiles deal with them. I think in > most cases these are just historical artifacts

Valery, That's pretty cute actually. Do you want this "brilliant" :) example in the cvs repository? I'd be happy to put it in. Reid. Valery A.Khamenya wrote: > Hi LLVMers, > > the example attached I have used to prove that JIT and some visible > optimizations are really invoked. > > Proved OK. I got 30% speed-up in comparison to gcc 3.3.3 >

On second thought, the makefiles don't (easily) allow this do they? You can only build one program per directory. Were you suggesting that you wanted me to move the entire directories under a "small examples" directory? Reid. Chris Lattner wrote: > On Tue, 17 Aug 2004, Reid Spencer wrote: > > >>That's pretty cute actually. Do you want this

Hi! I''m developing an localization plugin (just for my own purposes) and I wanted to extend the to_s method for the Time class. What I want to do: when someone does date.to_s(:short) that a localized version of the :short date is displayed. But I don''t know how to accomplish this. I know have this: class Time def to_s(option) print option.to_yaml

On Tue, 17 Aug 2004, Reid Spencer wrote: > On second thought, the makefiles don't (easily) allow this do they? You can > only build one program per directory. Were you suggesting that you wanted me to > move the entire directories under a "small examples" directory? You're right. The simples way to do this would be to have: projects/ SmallExamples/