search for: stkrc

...-cvs/llvm/projects/Stacker/lib/runtime' make[3]: Leaving directory `/home/wink/prgs/llvm-cvs/llvm/projects/Stacker/lib' make[3]: Entering directory `/home/wink/prgs/llvm-cvs/llvm/projects/Stacker/tools' make[4]: Entering directory `/home/wink/prgs/llvm-cvs/llvm/projects/Stacker/tools/stkrc' llvm[4]: Compiling stkrc.cpp for Debug build llvm[4]: Linking Debug executable stkrc llvm[4]: ======= Finished Linking Debug Executable stkrc make[4]: Leaving directory `/home/wink/prgs/llvm-cvs/llvm/projects/Stacker/tools/stkrc' make[3]: Leaving directory `/home/wink/prgs/llvm-cvs/llvm/...

On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > > Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. > This didn't work for me: > llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a > > I get two warning's about library 'crtend' missing > You didn't get the instructions quite right. The option is

Chris Lattner wrote: > On Sun, 26 Feb 2006, Wink Saville wrote: >> I then do the following in my makefile: >> >> llvm-gcc -c t1.c -o t1.bc >> llvm-gcc -c t1sub1.c -o t1sub1.bc >> llvm-gcc -c t1sub2.c -o t1sub2.bc >> llvm-ar r t1.a t1sub1.bc t1sub2.bc >> llvm-ar: creating t1.a >> llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a

...aren't a simple matter of grammar or correctness though. With some more complex things I don't have a clue what the "correct" way is supposed to be to even know what would be the appropriate area to patch. Something still seems wrong about the way that it is currently documented. stkrc is a good example. The page http://llvm.org/docs/ mentions stkrc among the list of "current tools". This tool is listed among the man pages on http://llvm.org/docs/CommandGuide/man/man1/ but it is not linked from more direct list of current tools on http://llvm.org/docs/CommandGuide/ It a...

...he changes, I now get: Global is external, but doesn't have external linkage! [1024 x int]* %_stack_ from the verifier. I tried changing the initial definition of TheStack to include an initializer with no modifications to it when there's a main. The produces the (somewhat expected): stkrc -e -f -o testing.bc /proj/work/llvm/projects/Stacker/test/testing.st llc -f -o testing.s testing.bc gcc -ggdb -L/proj/work/llvmobj/lib/Debug testing.s -lstkr_runtime -o eq eq.s /tmp/ccYV2ZHL.o(.bss+0x0):/proj/work/llvmobj/projects/Stacker/test/eq.s:10: multiple definition of `_stack_' /tmp/ccCl...

...use you can't (yet) specify the stack > size to the compiler! I'm debating the pros and cons of doing this. This sounds like something you could do much more cleanly with some sort of interprocedural analysis. You could stick that in your link-time Stacker optimizer. :-) For example: stkrc -c 1.st -o 1.o stkrc -c 2.st -o 2.o ... stkrc -c n.st -o n.o stkrld -o program 1.o 2.o ... n.o (links bytecode files, and does all the inter-procedural analysis and optimizations you need) We do stuff like this with gccld, for C/C++ programs. Hope this helps, -Brian -- gaeke at uiuc.edu

...s, 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 runtime library automatically using the "dependent libraries" feature of the VMCore IR. For example: bash-2.05$ llvmc fibonacci.st -o fibo -f -v stkrc -s 2048 fibonacci.st -o /tmp/llvm_1zyB4x/fibonac...

...river. The *only* requirement is that the tool be invokable with command line arguments. The driver tool is not expected to do anything but invoke other tools, so it needs to understand how to invoke a tool, what optimizations the tool supports, and what the output of that tool is. Let's take stkrc as an example. stkrc generates verbose, unoptimized byte code. It cannot generate LLVM assembly, native assembly, or native object files. Consequently, the driver would make up for its shortcomings by passing the .bc files to opt or llc in order to get optimizations done and to generate assembly, C...

...Index: lib/Transforms/Utils/CloneTrace.cpp Index: lib/VMCore/BasicBlock.cpp Index: lib/VMCore/Dominators.cpp Index: projects/Stacker/lib/compiler/StackerCompiler.cpp Index: projects/Stacker/lib/compiler/StackerCompiler.h Index: projects/Stacker/lib/runtime/stacker_rt.c Index: projects/Stacker/tools/stkrc/stkrc.cpp Index: projects/sample/include/sample.h Index: projects/sample/lib/sample/sample.c Index: projects/sample/tools/sample/main.c Index: test/Regression/C++Frontend/2003-09-22-CompositeExprValue.cpp Index: test/Regression/C++Frontend/2003-09-29-ArgumentNumberMismatch.cpp Index: test/Regressio...

...compiler/Lexer.cpp ? llvm/projects/Stacker/lib/compiler/StackerParser.cpp ? llvm/projects/Stacker/lib/compiler/StackerParser.h ? llvm/projects/Stacker/lib/compiler/StackerParser.output ? llvm/projects/Stacker/lib/runtime/Debug ? llvm/projects/Stacker/lib/runtime/Depend ? llvm/projects/Stacker/tools/stkrc/Debug ? llvm/projects/Stacker/tools/stkrc/Depend ? llvm/projects/sample/Makefile.common ? llvm/projects/sample/config.log ? llvm/projects/sample/config.status ? llvm/projects/sample/lib/Debug ? llvm/projects/sample/lib/sample/Debug ? llvm/projects/sample/lib/sample/Depend ? llvm/projects/sample/too...

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In

Ok, that makes sense :). , Tobias On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > > return *FieldPtr; > > > } > > > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > > cases? > > For the field pointer, one

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > return *FieldPtr; > > } > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > cases? For the field pointer, one could use the getelementptr instruction: %pairty = { sbyte, sbyte, int* } %pairPtr = ... %fieldptr = getelementptr

...compiler/Lexer.cpp ? llvm/projects/Stacker/lib/compiler/StackerParser.cpp ? llvm/projects/Stacker/lib/compiler/StackerParser.h ? llvm/projects/Stacker/lib/compiler/StackerParser.output ? llvm/projects/Stacker/lib/runtime/Debug ? llvm/projects/Stacker/lib/runtime/Depend ? llvm/projects/Stacker/tools/stkrc/Debug ? llvm/projects/Stacker/tools/stkrc/Depend ? llvm/projects/sample/Makefile.common ? llvm/projects/sample/config.log ? llvm/projects/sample/config.status ? llvm/projects/sample/lib/Debug ? llvm/projects/sample/lib/sample/Debug ? llvm/projects/sample/lib/sample/Depend ? llvm/projects/sample/too...

On Aug 24, 2007, at 1:52 PM, Holger Schurig wrote: > Is llvmc meant for compilation? > I'm not sure what the status of llvmc is (is anyone working on it?), but I don't believe it was ready for real use or was finished. If you would like to work on it, patches are welcomed! Thanks, Tanya > $ llvmc -c a.c -o a.o > /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output

Is llvmc meant for compilation? $ llvmc -c a.c -o a.o /usr/src/llvm/dist/etc/llvm/c:55: Error: Expecting output type value /usr/src/llvm/dist/etc/llvm/c had 1 errors. Terminating. The offending line contains: optimizer.output = bytecode which doesn't seem to be understood by llvmc. If I uncomment this line, I get another error message: $ llvmc -c a.c -o a.o llvmc: Can't find program