How about llvm-comp?
-Chris
.. not with this. I don't want to force compiler writers to have to make
yucky symlinks to llvm-driver. Also, I think it would be good for all
involved if they could think of LLVM (via their use of the driver) as
this magic black box that just gets compilation done, regardless of the
languages involved. Otherwise they will have to remember the weird
names used by all the language developers for all the different language
compilers. I'd rather hide that complexity from the user and just
provide them with a one-stop tool that does LLVM compilation. Its also
very useful for language developers to just "slot in" a new version of
the front end with appropriate configuration tools and the driver never
has to change.
Ok
As I said in my last message, I think the default behavior should be
that the driver works towards executing LLVM bytecode (in whatever way
appropriate) and we provide the -native option for those that want to
force the driver to produce native executables (but not native object
files!)
Ok, makes sense.
-Chris
Sorry, that makes no sense to me, and I am a compiler developer. 
`comp' is too common as a root of many words in common use --
`compare', `compassion', etc. On this list are `computer' and
`compiler', and that doesn't help things any.
That was my reaction too.
How about something along the notion of "build or construct" as in we
have two primary tools in llvm:
llvm-build - builds programs to be run
llvm-run - runs programs built by llvm-build
I'm not thrilled with llvm-build because its dull but from the
dictionary there is also:
llvm-construct (too long?)
llvm-make (obvious confusion)
llvm-forge (obscure)
llvm-erect (double entendre)
Reid.
How about something along the notion of "build or construct" as in we
have two primary tools in llvm:llvm-build - builds programs to be run
llvm-build or llvm-driver are both kinda long but at least they make
sense...
As an aside, llava and llama are both taken, llvmize? llvminator?
llvm-emerge a la gentoo?
llvm-run - runs programs built by llvm-build
Wait, is llvm-run the same as lli?
Or is it "compile to native, link, run native version"?
Or does it not matter?
I'm not thrilled with llvm-build because its dull but from the
dictionary there is also:llvm-construct (too long?)
llvm-make (obvious confusion)
llvm-forge (obscure)
llvm-erect (double entendre)
yeah, these aren't the most clear, easy-to-type-and-understand names.
llvm-build or llvm-driver are both kinda long but at least they make
sense...
Yeah, that's my sense too.
As an aside, llava and llama are both taken, llvmize? llvminator?
llvm-emerge a la gentoo?
Uh. No?
> llvm-run - runs programs built by llvm-build
Wait, is llvm-run the same as lli?
Or is it "compile to native, link, run native version"?
Or does it not matter?
I've been intending llvm-run (or possibly just llvm) to be the llvmee
that Vikram spoke about. In my mind its kinda like "java" in the Java
world. It executes bytecode in a variety of ways (interpreted, JIT, or
statically compiled) and includes the life-long optimization support
coming with the reoptimizer/profiler.
> I'm not thrilled with llvm-build because its dull but from the
> dictionary there is also:
>
> llvm-construct (too long?)
> llvm-make (obvious confusion)
> llvm-forge (obscure)
> llvm-erect (double entendre)yeah, these aren't the most clear, easy-to-type-and-understand names.
Yeah.
> llvm-build or llvm-driver are both kinda long but at least they make
> sense...Yeah, that's my sense too.
I agree, llvm-build or llvm-driver do have the handy effect of actually
meaning something.
-Chris
> As an aside, llava and llama are both taken, llvmize? llvminator?
> llvm-emerge a la gentoo?Uh. No?
>
> > llvm-run - runs programs built by llvm-build
>
> Wait, is llvm-run the same as lli?
> Or is it "compile to native, link, run native version"?
> Or does it not matter?I've been intending llvm-run (or possibly just llvm) to be the llvmee
that Vikram spoke about. In my mind its kinda like "java" in the Java
world. It executes bytecode in a variety of ways (interpreted, JIT, or
statically compiled) and includes the life-long optimization support
coming with the reoptimizer/profiler.>
> > I'm not thrilled with llvm-build because its dull but from the
> > dictionary there is also:
> >
> > llvm-construct (too long?)
> > llvm-make (obvious confusion)
> > llvm-forge (obscure)
> > llvm-erect (double entendre)
>
> yeah, these aren't the most clear, easy-to-type-and-understand names.Yeah.
-Chris
I place a vote for llvm-build.
Misha Brukman wrote:
How about something along the notion of "build or construct" as in we
have two primary tools in llvm:llvm-build - builds programs to be run
llvm-build or llvm-driver are both kinda long but at least they make
sense...As an aside, llava and llama are both taken, llvmize? llvminator?
llvm-emerge a la gentoo?
Actually, I like llama. It sounds cool.
Anybody got an idea of what it could stand for?
-- John T.