[LLVMdev] Compiler Driver [high-level comments]

[Chris Lattner]

On Mon, 2 Aug 2004, Reid Spencer wrote:

> I have a very simple XML document type that I use for configuring XPS
> systems. There's only four elements and it follows much the same kind of
> grouped name/value pairs that Chris is suggesting. Chris' example would
> be like:
> <configuration name="llvm">
>  <group name=".c">
>    <item name="compile">cc1 %in -o %out</item>
>    <item name="optimize">gccas %in -o %out.bc</item>
>    <!-- ... -->
>   </group>
> </configuration>
>
> I think something like this satisfies all the goals:
> * simple and easy; recursive descent parser is a no-brainer
> * XML format with full DTD (RNG or XML Schema) that can be used by other
>   tools to auto-configure llvmcs
> * structured so we can extend in the future

Okay, if you get all of the benefits without the cost, go for it :)

-Chris


> On Mon, 2004-08-02 at 22:22, Chris Lattner wrote:
> > On Tue, 3 Aug 2004, Bill Wendling wrote:
> > > I admit a bias here: I've worked with MS style INI files. They didn't
> > > leave a good impression with me. However, they do fit the bill for a lot
> > > of applications. What do you envision a typical INI file to look like?
> >
> > I was thinking of something simple like this:
> >
> > [.c]
> >
> > compile  = cc1 %in -o %out
> > optimize = gccas %in -o %out.bc
> > link     = gccld ...
> >
> > [.cpp]
> >
> > compile  = cc1plus %in -o %out
> > ...
> >
> > etc.  Something like that.  The exactly details are still very much up in
> > the air, but just simple key/value pairs is all we should need.
> >
> > -Chris
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>

-Chris

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