There are many parallel programming compilers and libraries. Which one is good for you?
Michael Wolfe, Compiler Engineer at The Portland Group, Inc., writes an article on many available options that claim to make parallel programming easy, discusses complexity of parallelism, and offers a few methods for solving the current “parallelism crisis”.
“The current “parallelism crisis” can only be resolved by three things. First, we need to develop and, more importantly, teach a range of parallel algorithms… Second, we need to expand algorithm analysis to include different parallelism styles. It’s not enough to focus on just the BSP or SIMD or any other model; we must understand several models and how they map onto the target systems…Finally, we need to learn how to analyze and tune actual parallel programs.”
“Parallel processing is an obstacle, but then so is sequential processing. Parallel computing can result in better productivity, efficiency, and accuracy in the scientific process overall, but it’s silly to think that it will result in better productivity and efficiency in the programming process itself. The best we can hope for is to make parallel programming not much harder than sequential programming.”



3 responses so far ↓
1 Why not teach ONLY parallel programming? // Sep 8, 2008 at 6:06 pm
[...] complex and difficult to program. Clay Breshears, in response to Michael Wolfe’s “Compilers and More: Parallel Programming Made Easy?” column, writes that teaching only parallel programming from Day 1 as a solution to make [...]
2 What is so Hard About Parallel Programming? // Sep 17, 2008 at 2:13 pm
[...] response to Michael Wolfe’s “Compilers and More: Parallel Programming Made Easy?” column, Clay Breshears, ten days ago wrote a blog titled, “Why not teach ONLY parallel [...]
3 Thoughts on the endstate of multicore software development by Max Domeika // Sep 20, 2008 at 10:48 am
[...] Domeika writes a blog post expressing his views after reading two articles: 1) Compilers and More: Parallel Programming Made Easy? and 2) Twilight of the GPU: an interview with Tim [...]