similar to: [LLVMdev] Automatic Loadable Linker Optimization Modules

On 7/25/05, Reid Spencer <reid at x10sys.com> wrote: > I think that the answer is that llc is intended to be the final compiler > of executable output. Running "general" passes in llc was never part of > the design. It just runs machine passes, assuming that its bytecode > input is already optimized. OK, that makes sense. > What you're looking for is a program

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

On Tue, 22 May 2007 23:52:46 -0700 (PDT) Chris Lattner <sabre at nondot.org> wrote: >On Sun, 20 May 2007, Bram Adams wrote: >> On a related note: while using llvmc I have some test cases where the >> following error now pops up on Linux X86 (not on OSX): >> >> <premain>: CommandLine Error: Argument 'debug' defined more than once! >> llvmc:

When I build LLVM, the message LLVMHello ignored -- Loadable modules not supported on this platform is shown and the LLVM Hello pass doesn't work. I am using Windows. Is this correct? LLVM Hello pass works only on Linux? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

On Mon, 2006-11-20 at 17:49 +1100, Emil Mikulic wrote: > I've compiled all the object files that make up libstdc++ and libsupc++ > into LLVM bytecode: > http://goanna.cs.rmit.edu.au/~emil/libstdcxx.tar.bz2 (438KB) > > A simple test program, x.cpp: > > #include <iostream> > int main() { std::cout << "hello world\n"; return 0; } > > $

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

I've compiled all the object files that make up libstdc++ and libsupc++ into LLVM bytecode: http://goanna.cs.rmit.edu.au/~emil/libstdcxx.tar.bz2 (438KB) A simple test program, x.cpp: #include <iostream> int main() { std::cout << "hello world\n"; return 0; } $ llvm-g++ -emit-llvm -c x.cpp $ llvmc -o=out x.o std/*.o sup/*.o $ lli out.bc Segmentation fault (core

On Mon, 2006-11-20 at 17:49 +1100, Emil Mikulic wrote: > I've compiled all the object files that make up libstdc++ and libsupc++ > into LLVM bytecode: > http://goanna.cs.rmit.edu.au/~emil/libstdcxx.tar.bz2 (438KB) > > A simple test program, x.cpp: > > #include <iostream> > int main() { std::cout << "hello world\n"; return 0; } > > $

On Mon, Nov 20, 2006 at 08:01:23AM -0800, Reid Spencer wrote: > On Mon, 2006-11-20 at 17:49 +1100, Emil Mikulic wrote: > > I've compiled all the object files that make up libstdc++ and libsupc++ > > into LLVM bytecode: > > http://goanna.cs.rmit.edu.au/~emil/libstdcxx.tar.bz2 (438KB) > > > > A simple test program, x.cpp: > > > > #include

Hi folks, I'm trying to compile VMKit (and eventually J3) with LLVM/Clang head. There seem to be some recent commits (starting with roughly 165505) that break the VMKit compile with the following errors: $ make ENABLE_OPTIMIZED=1 llvm[0]: Constructing LLVMBuild project information. make[1]: Entering directory `.../vmkit/lib/vmkit/StaticGCPass' llvm[1]: Compiling StaticGCPass.cpp for

On Mon, 2005-07-25 at 21:48 -0700, Michael McCracken wrote: > On 7/25/05, Reid Spencer <reid at x10sys.com> wrote: > > Why not just create your pass as a shared object and: > > > > opt -load mypass.so -mypass | llc > > My pass is an implementation of an analysis group that I wanted to > make available to machine passes as well as optimization passes. So I >

Hello all, Is it well known that building LLVM with --enable-optimized causes RegisterPass calls to be removed from dynamically loadable libraries (i.e., those built with LOADABLE_MODULE=1)? For example, here's what happens to the Hello pass (ToT on Darwin, both with and without --enable-optimized): $ pwd /Users/ransford/llvm/lib/Transforms/Hello $ nm -j Release+Asserts/Hello.o | c++filt -p

shding at mtu.edu wrote: > Hi, > Where can I find the main function of llvm compiler in the source file? > Thanks! Well, there's a loaded question. :) It depends on "which" compiler you mean. If you're talking about the llvm-gcc and llvm-g++ compilers (C/C++ to LLVM) then they are in the downloadable tarballs available here: http://llvm.cs.uiuc.edu/releases/. You

Here is the bulk of the sanitizing. My residual doubts center around the question whether we still do/want to support (un)compressed *byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached

Hi, In writing llvmc, I need to link in the Bytecode reader in order to extract the "dependent libraries" from the bytecode files. And, bytecode reader needs vmcore. And, vmcore has a static cl::opt<bool> named "EnableTiming" for the -time-passes option. This conflicts at runtime with llvmc's -time-passes option (which it passes through to sub-tools). So, my

On Sun, 2003-11-16 at 10:44, Chris Lattner wrote: > > In other words, I'd like to take a set of bytecode files, optimize them > > together even though they don't form a complete program, and then write > > out the new (optimized) bytecode files. It would be preferable to write > > them out to a single archive rather than to individual bytecode files > >

Thank you. I'm only consider about how the compiler comiles c program to LLVM IR. I know there should be a scanner, parser, and IR generator. But where is the main entrance and how about the flow of the process, especially about the IR generator? > shding at mtu.edu wrote: >> Hi, >> Where can I find the main function of llvm compiler in the source >> file? >>

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. You write your compiler to generate either bytecode or LLVM assembly and a configuration file. The rest of it (optimization, linking, codegen) can be done with existing LLVM tools. If you later want to include those features in your compiler, you can

The recent change in the library structure to make libLLVMCore.a instead of LLVMCore.o has caused a little fallout. The problem is LLVM tools that take a --load option to load a module dynamically may now cause those modules to fail to load at runtime. This occurs because the tool with the --load option might not be linking in all of libLLVMCore.a, but only the object modules actually needed by