Hi Charlie, Have many thanks! I can now also confirm BOINC to build with clang. A couple of warnings are left, but those also appear with the gcc.
Cheers, Steffen > Gesendet: Donnerstag, 30. Mai 2013 um 03:28 Uhr > Von: "Charlie Fenton" <[email protected]> > An: "Steffen Möller" <[email protected]> > Cc: "[email protected]" <[email protected]> > Betreff: Re: [boinc_dev] prepared to accept patches for llvm, i.e. clang, > compatibility? > > Hi Steffen, > > For what it's worth, I have been building BOINC on the Mac using the "LLVM > GCC 4.2" compiler for quite some time with no problems. (This is one of two > compilers provided as part of Xcode 4.4.1, the other is "Apple LLVM Compiler > 4.0".) > > According to Apple's documentation: > > In Xcode, the LLVM compiler uses the Clang front end (a C-based languages > > project on LLVM.org) to parse source code and turn it into an interim > > format. Then the LLVM code generation layer (back end) turns that interim > > format into final machine code. Xcode also includes the LLVM GCC compiler, > > which uses the GCC compiler front end for maximum compatibility, and the > > LLVM back end, which takes advantage of LLVM's advanced code generator. > > > Cheers, > --Charlie > > On May 29, 2013, at 1:02 AM, Steffen Möller wrote: > > > Hello, > > > > The compiler LLVM (http://en.wikipedia.org/wiki/Clang) makes continuous > > progress, both technically and for its acceptance in the community, and is > > faster than gcc/g++ in some cases. They have a gcc-compatibility frontent > > called "clang", which after a <fun>countable number of patches</fun> I > > could run on BOINC already about a year or two ago. Also shipping are tools > > for code analysis which may be of general interest - to the development of > > BOINC but possibly even more so for the developers of the scientific > > applications. > > > > There is an effort by Debian to recompile the whole archive with clang, > > http://clang.debian.net/ , completely independent of this request. It gives > > an overview of issues typically found. From what I recall, for BOINC there > > was nothing that IMHO could not possibly be tolerated, even when there is > > no gain in functionality, and nothing that would change the API. I would > > volunteer to redo that past effort, if there are some voices from the > > community, especially David's, to appreciate it. My driving force is less > > on the benefits for the BOINC client than about the extra confidence for > > the application developers to just go and try that alternative to g++ that > > they have heard so much about but just not got around to run. > > > > Cheers, > > > > Steffen > > _______________________________________________ > > 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. > > > > _______________________________________________ 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.
