[cfe-commits] [cfe-dev] Switching http://llvm.org/demo to clang or providing a separate clang demo

David Blaikie dblaikie at gmail.com
Tue Aug 30 22:31:43 PDT 2011

> Why not build a bunch of cross-compilers, and use the right one depending
>>> on the
>>> target?
>> I honestly don't know what it takes to setup a cross compiler, and I
>> wouldn't be the one doing it - I expect this would fall on Tanya's plate.
>> Not worth the maintenance cost IMO.
> With that in mind, then, here's a modified version of Bjarke's patch that
> only provides 4 targets (x86, x86-64, llvm bitcode, llvm C++ api). I also
> stripped out Bjarke's work to support multiple front ends (llvm-gcc and
> clang) - I thought about preserving it or switching it to dragonegg, but I'm
> not sure that's worthwhile or in the domain of the llvm demo page.
> & I stripped out some old file types/extensions that clang doesn't support
> (Java, Fortran) while I was here.

& I believe this should adequately address
http://llvm.org/bugs/show_bug.cgi?id=1440 based on the discussion we've had

(& I also switched index.cgi to post to index.cgi rather than test.cgi - I
assume this was just a minor slip-up in the last commit to index.cgi)

- David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20110830/2a8db240/attachment.html>

More information about the cfe-commits mailing list