[cfe-dev] alternate clang driver
rkotler at mips.com
Thu Oct 20 15:00:51 PDT 2011
I'm not really trying to sell people on another tool.
It's there if someone else wants to use it.
I found the clang driver to be overly complex and it was slowing down my
development and to me it should have taken about 10 minutes to set up a
new port and instead it involved lots of study and doing lots of
hardcoding regarding specific directories to search and may other such
things in the compiler which I find fundamentally wrong.
With my driver, I could do new ones in no time and make simple install
scripts so it can be configured for specific users machine.
I have to fix the builtin clang driver for Mips too and am working on
But I find that driver to be fundamentally problematic. It's just my
Differences of opinion is what makes horse races.
On 10/20/2011 10:51 AM, David Chisnall wrote:
> Can you tell us a little bit more about what makes this different? I use clang for cross-compiling for ARM, and invoking clang as arm-none-linux-gnueabi-clang, or as clang -ccc-host-triple arm-none-linux-gnueabi enables it to find all of the other bits of the toolchain fine - I'm using it as an almost drop-in replacement for gcc in the WebOS PDK, which shipped with gcc. The only difficulty it had was finding the various tools, since the Linux toolchain stuff ignores -B, but this was solved with a few symlinks into the sysroot...
> On 20 Oct 2011, at 18:04, Reed Kotler wrote:
>> We have developed an alternate clang driver and placed it as open source
>> in google code.
>> Most people are using cross compilers for MIPS. We needed something
>> different than what the clang driver provides us at this time.
>> This driver behaves enough like gcc cross drivers for us to run make
>> files and other things meant for gcc right out of the box. We have for
>> example run dejagnu gcc using it with no problems.
>> It's still in development but it works very well for us right now.
>> I intended to put more documentation for it before announcing it but our
>> schedules are overloaded now and I can't assign anyone to do that for
>> the next 2 months so I decided to just announce it now.
>> We can put resources into bug fixing and extensions but we already know
>> how it works so it's not essential for us to do more docs at this time. :)
>> It's a simple program and written in python and I think it's pretty easy
>> to understand from just looking at the code.
>> We welcome other people to help make it work better for more platforms
>> than just MIPS.
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
More information about the cfe-dev