[LLVMdev] Compiler Driver Decisions

[Chris Lattner]

On Tue, 3 Aug 2004, Reid Spencer wrote:
> .. 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

-- 
http://llvm.cs.uiuc.edu/
http://nondot.org/sabre/