Linked by Thom Holwerda on Wed 7th Nov 2012 23:50 UTC, submitted by Joel Dahl
FreeBSD "I've made clang the default on x86 systems. There will probably be a few bumps as we work out the last kinks including a ABI issue for i386 system libraries, but the transition is expected to be fairly smooth for most users."
Thread beginning with comment 541433
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: why?
by kwan_e on Thu 8th Nov 2012 14:12 UTC in reply to "RE[4]: why?"
Member since:

Thanks for the link. The site says that cling is an "interactive interpreter" for the C++ language, thus I figure it is something like "ipython" is for Python?

From what I understand, it's more like an interactive version of a "JVM" for C++. It's made possible due to the parser and the intermediate language and the JIT-optimizer being in completely separate modules. So you can enter C++ code and it will recompile, optimize and link behind the scenes on the fly.

CERN surely does HPC, but I bet their parallel codes were developed using MPI, which is a completely different technique and is supported by clang. Our codes rely both on MPI and OpenMP, and changing them to remove the dependency from the latter would be a huge (and useless) pain.

Well I wouldn't have thought you'd change your existing OpenMP code to MPI just for the sake of it. There's no reason for any code to move to clang just for the sake of it either. You'd probably want to try it out with a small MPI project rather than make a full commitment to clang just for the sake of it.

Reply Parent Score: 2