similar to: [LLVMdev] BitterMelon Gets Stackered

Hi Lalo, Its been a while since I've had a Stacker question! The answer is in the StackerCompiler::handle_while function in StackerCompiler.cpp in projects/Stacker/lib/compiler. Apparently the control value is only examined (not popped) for the "WHILE" operator. Take for example the prime.st sample program. The first thing it does is process the arguments with a WHILE loop:

Folks, As of the writing of this note, the llvmc tool is enabled for build on the CVS head. I'm encouraging you to try it out, provide some feedback, and help with the issues below. llvmc is now able to correctly link a pure bytecode version of any Stacker program. This includes translation with stkrc, optimization with opt and linking with llvm-link. It is also able to find Stacker's

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,

On Wed, 21 Jul 2004, Chris Lattner wrote: > > Yes, this makes a tremendous amount of sense. Do you think you could > prepare some patches to make this happen? If you have any questions, feel > free to ask :) Ok, a patch[1] is attached. I didn't care to coerce the offset, since I assume that it is an uint, but maybe I should? Hopefully I've understood the llvm source

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 (attached)... sorry about the fax-quality scan. But I have some questions about it... -

Ok, here's the new patch. (Please tell me if I shouldn't mail patches directly on the mailing list.) While I was editing LowerGC.cpp I made a little test (not part of this patch, but the diff with LowerGC.cpp in cvs is attached). I've added a new intrinsic called llvm.gcroot_value(sbyte*, sbyte*), which takes a pointer directly instead and transforms it into an alloca. The idea is the

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 >

Having recently become interested in llvm I've read a lot of documentation on your website. Considering that a 2.5 release is due out soon, I'm guessing there will be additional readers and writers focusing on the docs. Would feedback in this area be welcome? Simple misspellings of words on various pages like Subvresion, producess, performsn, instructiosn, catagory, and mis-behaving seem

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 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

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/

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

On Tue, 17 Aug 2004, Reid Spencer wrote: > That's pretty cute actually. Do you want this "brilliant" :) example in the cvs > repository? I'd be happy to put it in. Here's an idea: how about we take the ModuleMaker, Valery's previous example, and this one and put them all in one "small examples" project? -Chris > Valery A.Khamenya wrote: > >

Hi guys, there are few issues concerning LLVM and Gento Linux below. 1. Gentoo encourages to think of smarter packaging. Oversimplified, but... there are at least three audiences using LLVM: - application users - developers *using* LLVM in their projects - developers *changing* LLVM sources. Application users are not interested in LLVM, they are rather interested to have their favorite

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

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

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 :=

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