More or less following a plan during design: opportunistic deviations in specification
International Journal of Man-Machine Studies - What programmers know
Knowledge exploited by experts during software system design
International Journal of Man-Machine Studies - What programmers know
Is data distribution necessary in OpenMP?
Proceedings of the 2000 ACM/IEEE conference on Supercomputing
Software design---cognitive aspects
Software design---cognitive aspects
SPMD OpenMP versus MPI on a IBM SMP for 3 Kernels of the NAS Benchmarks
ISHPC '02 Proceedings of the 4th International Symposium on High Performance Computing
Models of parallel computation: a survey and synthesis
HICSS '95 Proceedings of the 28th Hawaii International Conference on System Sciences
affinity-on-next-touch: increasing the performance of an industrial PDE solver on a cc-NUMA system
Proceedings of the 19th annual international conference on Supercomputing
ARCS '09 Proceedings of the 22nd International Conference on Architecture of Computing Systems
Implementing irregular parallel algorithms with OpenMP
Euro-Par'06 Proceedings of the 12th international conference on Parallel Processing
Performance evaluation of OpenMP-based algorithms for handling Kronecker descriptors
Journal of Parallel and Distributed Computing
Hi-index | 0.00 |
The OpenMP standard defines an Application Programming Interface (API) for shared memory computers. Since its introduction in 1997, it has grown to become one of the most commonly used API's for parallel programming. But success in the market doesn't necessarily imply successful computer science. Is OpenMP a "good" programming environment? What does it even mean to call a programming environment good? And finally, once we understand how good or bad OpenMP is; what can we do to make it even better? In this paper, we will address these questions.