similar to: [LLVMdev] RE: LLVM languages cooperation

Chris Lattner wrote: > BTW, you might want to check out this document that Reid wrote, which > >describes his experiences writing a front-end for LLVM, and giving lots of >hints and tips: http://llvm.cs.uiuc.edu/docs/Stacker.html > > Thanks, I already had a quick look on it. Also thanks for your explanation on how the C++ back-end converts function calls to LLVM code. As

On Tue, 24 Feb 2004, [ISO-8859-1] S�bastien Pierre wrote: > In this respect, it might be interesting to come up with guidelines (or > maybe something more "formal") for back-end developers to write such > cross-language communication runtime. Sure, that sounds like a very worthwhile project, but also a hard one. :-) > As LLVM seems to offer a language-independant type

On Tue, 24 Feb 2004, Vikram S. Adve wrote: > LLVM does define a common function call and struct/array/pointer model. You > could use that to define a language-interoperability scheme, but I think it > would require some special support from the front-ends to translate > functions exposed to a different language to conform with the scheme, or to > generate wrappers for them. For

Hello Chris, Chris Lattner wrote: >This really stems from >differing goals, though LLVM can certainly be used to compile MSIL-like >systems, so it's just a matter of specifying the rules and making the >front-ends stick to them. :) > > Ok, this is clear. Do you plan any "foreign function interface" or something similar that would ease, if not automate

Hi all, I am an LLVM newbie, thinking about using LLVM as the platform for a toy language. In this respect, I was wondering if LLVM could be used to easily weave code written in different language. For instance, let's assume I have a library written in C, some components written in C++ and some components written in OCaml (we also assume an OCaml backend for LLVM). All this code gets

Reid Spencer wrote: > 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

Hi, I get this error: --------------- configure: configuring in projects/Stacker configure: running /bin/sh '/C/projects/src/llvm-2/llvm/projects/Stacker/configure' --prefix=/C/LLVM/tools/ '--prefix=/C/LLVM/tools/' 'CPPFLAGS=-D__MINGW -DLLVM_ON_WIN32=1' --cache-file=/dev/null --srcdir=/C/projects/src/llvm-2/llvm/projects/Stacker configure: error: invalid variable

All, I'm finding the current layout a bit frustrating, not to mention that it breaks all the documentation. We currently have modules laid out like this: llvm/trunk/... llvm/branches/... llvm/tags/... stacker/trunk/... stacker/branches/... stacker/tags/... and similarly for all the other modules (test-suite, java, poolalloc, etc.). Unfortunately, this "standard"

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

Reid, Click on any of these logs and you'll see the same asm parsing issues. It's been going on for much of the week. http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build (bytecode)

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

On Fri, 2003-12-19 at 15:32, Chris Lattner wrote: > This is intentionally not part of the LLVM type-system, because it is > redundant. If you compile a C program that uses a union, for example, the > C front-end will turn it into a type (often a structure) that contains > only one of the element types (usually the largest one, perhaps modified > to have the correct alignment).

On Fri, 19 Dec 2003, Reid Spencer wrote: > As a side effect of bug 178 (Stacker not handling 64-bit pointers on > Solaris), I got thinking about a union type for LLVM. Is there any > good reason that LLVM shouldn't support unions? This is essentially a > structure that has its members all at the same address rather than at > sequential addresses. I know there are various

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

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

Reid Spencer wrote: > Yes, that's right! > > In fact, shortly the process of doing that will get easier with the > llvmc (compiler driver) tool that I'm working on. [another newbie delurks] Hi, Reid. Been tinkering with LLVM about 2 weeks now. I've been using the Stacker Compiler as an example so far for my own little project. Is this tool you mentioned coming

My hat is off to everyone that's worked on LLVM. I started coding Stacker yesterday from scratch as a background task in between doing "real" :) work. Tonight I got my first program generated by the Stacker compiler to compile, link and execute. The entire control flow of Stacker is done (mind you its trivial). All that remains is to fill in code generation for about 60 built-in

Next problem detected by nighttest: LLVM build fail with errors: gmake[4]: Entering directory `/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime' llvm[4]: Compiling stacker_rt.c for Debug build (bytecode) default/bin/llvm-gcc: not found gmake[4]: *** [/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime/Debug/stacker_rt.bc] Error 1

Jim Laskey wrote: > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build > (bytecode) > /Volumes/Muggles/LLVM/nightlytest/build/llvm/Release/bin/gccas: / > Volumes/Muggles/LLVM/nightlytest/build/llvm/projects/Stacker/lib/ > runtime/Release/stacker_rt.ll:21,0: parse error, expecting `LOAD' or > `STORE' >