Linked by Thom Holwerda on Wed 7th Nov 2012 23:50 UTC, submitted by Joel Dahl
Permalink for comment 541433
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2007-02-18
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.
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.