On Jun 25, 2010, at 8:35 PM, Eric J Korpela wrote: > On Fri, Jun 25, 2010 at 5:17 PM, David Anderson <[email protected]> > wrote: >> Bundling LLVM with the BOINC client means that: >> 1) LLVM apps won't work with existing BOINC clients >> 2) Projects can't control which version of LLVM is used >> Including LLVM with the app itself solves these problems. > > What license is LLVM compiled under. Is it freely distributable under > any license? > LLVM is the University of Illinois/NCSA Open Source License, which is BSD or MITish. It's GPL compatible.
> It's better to have LLVM in the BOINC client (or require it to be > installed). Then it just means adding a new platforms that the client > can report whether it supports that platform. For example > theplatforms could be "genericunix-LLVM", "linux-LLVM", > "windows-LLVM", "macos-LLVM" > > LLVM provides a generic compiler. It doesn't AFAIK provide a generic > API. So the scheduler probably still needs to know the appropriate > platform unless everything is to be written in standard C. LLVM isn't really a compiler. It's supposed to be a language independent framework for writing compilers. There are then various frontends for C, C++, Objective C, and more recently Haskell and Python, as well as others. clang is a C compiler using LLVM as the backend, and offers an API for the Cs. Clang is meant to be easily embedded in other applications, and why the majority of OpenCL implementations now use clang with LLVM to compile the CL kernels at runtime. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
