------- Comment #7 from danny dot dyk at tu-dortmund dot de 2008-08-10 22:49 ------- Applicable to a subset of C++ doesn't equal C++ compatibility.
I'm fine with OpenMP unable to successfully parallelise a majority of possible for loops. It's quite understandable. However, instead of throwing error messages it should keep these for loops singlethreaded and issue a warning. G++ is a C++ compiler, not an OpenMP compiler. The -fopenmp switch should not alter the perception of what is valid code and what not. Now, is there any part in the OpenMP standard that forces a valid implementation to bring all OpenMP directives to effect? Or is it OK to just issue warning? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35158
