[cfe-dev] RFC: Clang driver redesign

[Clark Gaebel]

Good point(s). In that case, it can be a trivial C++ program which does
find/replace on the arguments and execs clang with the interpreted
arguments. The point is that it doesn't have to be anything fancy.

On Tue, Nov 8, 2011 at 11:09 AM, James Molloy <james.molloy at arm.com> wrote:

> ... and doesn't work on windows :)
>
> -----Original Message-----
> From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] On
> Behalf Of Konstantin Tokarev
> Sent: 08 November 2011 16:08
> To: Clark Gaebel
> Cc: clang-dev Developers
> Subject: Re: [cfe-dev] RFC: Clang driver redesign
>
> 08.11.2011, 19:34, "Clark Gaebel" <cg.wowus.cg at gmail.com>:
> > What's wrong with having a gcc compatibility layer for the driver which
> just translates from one option set to the other. I'm thinking of something
> like:
> >
> > clang-gcc [gcc options]
> > clang-g++ [g++ options]
> >
> > clang [clang options]
> > clang++ [clang++ options]
> >
> > If anything, the clang-gcc and clang-g++ could just be shell script
> wrappers around clang.
>
> Using shell for argument conversion can introduce noticeable performance
> penalty.
>
> --
> Regards,
> Konstantin
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20111108/bf508762/attachment.html>