search for: llvmcd

> On Mon, Aug 02, 2004 at 06:05:16PM -0700, Reid Spencer wrote: > > On Mon, 2004-08-02 at 18:04, Chris Lattner wrote: > > llvmcd - llvm compiler driver > > llvmci - llvm compiler invoker > > llvmcs - llvm compiler system (or perhaps "compilation system") > > llvmct - llvm compiler tool > > llvmx - llvm eXecutive > > I like llvmcs. Contrary to the IRC discussion, I am not sure I want...

On Tue, Aug 03, 2004 at 12:26:50PM -0500, Brian Gaeke wrote: > > On Mon, Aug 02, 2004 at 06:05:16PM -0700, Reid Spencer wrote: > > > On Mon, 2004-08-02 at 18:04, Chris Lattner wrote: > > > llvmcd - llvm compiler driver > > > llvmci - llvm compiler invoker > > > llvmcs - llvm compiler system (or perhaps "compilation system") > > > llvmct - llvm compiler tool > > > llvmx - llvm eXecutive > > > > I like llvmcs. Contrary to the IRC di...

...). Unfortunately this leads me to vote against llvmcs -- it's vague and (worse) a misnomer. A "system" to a program or a compiler driver or an invoker or anything specific like that. *LLVM* is a system; this program is a program with a more limited purpose. Of the list below, llvmcd comes closest to describing what this tool does. Another possible name is llvmgen (even though I do think it should have options to compile to native code). This fits slightly better with my view of how users should view the compilation process in LLVM (but llvmcd is ok too). I would like to...

...the compiler". What it does do is invoke those compilers. Because it can invoke many of those language compilers, even multiple on the same execution, the notion of "compiler collection" is pretty accurate. However, if you want to avoid the cc suffix, lets explore some alternatives: llvmcd - llvm compiler driver llvmci - llvm compiler invoker llvmcs - llvm compiler system (or perhaps "compilation system") llvmct - llvm compiler tool llvmx - llvm eXecutive Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: applicat...

...e "normal" and default case. > > (2) Once the dynamic optimizer Brian and Tanya and Anand have worked > on is ready for distribution, I would like to make llvmee (Misha's > llvm execution environment) the expected, default way to run llvm > programs. The llvm driver (llvmcd or llvmgen or whatever name we > pick) would generate llvm code that is later compiled and run > transparently by llvmee. Whether the code generation to native code > happens offline (via llc) or on-line (via the jit) can be controlled > via llvmee. Again, this requires reinforcing th...

On Mon, Aug 02, 2004 at 06:05:16PM -0700, Reid Spencer wrote: > On Mon, 2004-08-02 at 18:04, Chris Lattner wrote: > llvmcd - llvm compiler driver > llvmci - llvm compiler invoker > llvmcs - llvm compiler system (or perhaps "compilation system") > llvmct - llvm compiler tool > llvmx - llvm eXecutive I like llvmcs. Contrary to the IRC discussion, I am not sure I want a hyphen in this ... Without...

Hi LLVM'ers If I may chime in to your discussion about naming the compiler-driver. As a newcomer (and novice) about LLVM, but as user, I think users best understand llvmcd (or llvm-driver) in conjunction with the runtime environment llvmee (or llvm-run). If I had to choose, and personnally I don't like those cryptic acronyms or other short hand forms, I'll pick up the names llvm-driver and llvm-run. /Henrik >From: Chris Lattner <sabre at nondot.o...

...s done with #!<interpreter>. I believe ELF provides similar functionality (where exec()ing the file can load a program or library to do JIT compilation), but if it doesn't, then we lose this feature. o Compiler Driver Name I'd vote for either llvmcc (llvm compiler collection) or llvmcd (llvm compiler driver). To be more convenient, we could call it llc (LLvm Compiler) or llcd (LLvm Compiler Driver). Calling it llc would require renaming llc to something else, which might be appropriate since I view llc as a "code generator" and not as a "compiler" (altho...

LLVMers, Since there's been little feedback on the design document I sent out, some decisions are being made in order to progress the work. If you have strong feelings about any of these, voice them now! 1. Name = llvmcc 2. The config file format will resemble Microsoft .ini files (name=value in sections) 3. -O set of options will control what gets done and what kind of output is

...ly this leads me to vote against llvmcs -- it's vague and > (worse) a misnomer. A "system" to a program or a compiler driver or an > invoker or anything specific like that. *LLVM* is a system; this > program is a program with a more limited purpose. Of the list below, > llvmcd comes closest to describing what this tool does. I don't like llvmcs either, though I don't know of a good name. The problem is that we are entering the realm of LLVM as a *compiler* not as a bunch of utilities for building compilers. As such, the compiler driver (which is an LLVM tool)...

...gt; does do is invoke those compilers. Because it can invoke many of those > language compilers, even multiple on the same execution, the notion of > "compiler collection" is pretty accurate. However, if you want to avoid > the cc suffix, lets explore some alternatives: > > llvmcd - llvm compiler driver > llvmci - llvm compiler invoker > llvmcs - llvm compiler system (or perhaps "compilation system") > llvmct - llvm compiler tool > llvmx - llvm eXecutive How about llvm-foo? We can retroactively come up with the meaning for foo later :) Alternatively...

On Tue, 3 Aug 2004, Reid Spencer wrote: > > For the name, again, I'd be happy with either llvmcd or llvmgen, witha > > preference for the latter. The more important thing is to makellvm > > code be the default output. > > I'm not thrilled with llvm-gen because it has overtones of "code > generation" (which actually isn't far from the truth). But, it con...

On Mon, 2 Aug 2004, Reid Spencer wrote: > I actually like Misha's point here. Most people that have used GCC > recently realize that the CC means "Compiler Collection" and not "C > Compiler" which is appropriate given what it does. Since we intend to be > front end language agnostic and the driver tool will support multiple > front end languages,

...vote against llvmcs -- it's vague and > > (worse) a misnomer. A "system" to a program or a compiler driver or an > > invoker or anything specific like that. *LLVM* is a system; this > > program is a program with a more limited purpose. Of the list below, > > llvmcd comes closest to describing what this tool does. > > I don't like llvmcs either, though I don't know of a good name. The > problem is that we are entering the realm of LLVM as a *compiler* not as a > bunch of utilities for building compilers. As such, the compiler driver >...

On Mon, 2004-08-02 at 17:31, Chris Lattner wrote: > On Mon, 2 Aug 2004, Misha Brukman wrote: > > > On Mon, Aug 02, 2004 at 07:23:06PM -0500, Chris Lattner wrote: > > > > > > 1. Name = llvmcc > > > > > > > > > > Why not 'llvmc' "llvm compiler"? What does the extra C mean? > > > > > > > > I dunno.

...t; > Here are the disadvantages I see: > > 1) Increased disk usage. For example, symbol table information would > duplicate the information already in the bytecode file. Right ;> > o Compiler Driver Name > > I'd vote for either llvmcc (llvm compiler collection) or llvmcd (llvm > compiler driver). To be more convenient, we could call it llc (LLvm > Compiler) or llcd (LLvm Compiler Driver). Calling it llc would require > renaming llc to something else, which might be appropriate since I view > llc as a "code generator" and not as a "c...