[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-20 Thread manu at gcc dot gnu dot org
--- Comment #10 from manu at gcc dot gnu dot org 2008-08-20 16:36 --- Subject: Bug 35158 Author: manu Date: Wed Aug 20 16:35:21 2008 New Revision: 139335 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=139335 Log: 2008-08-20 Manuel Lopez-Ibanez [EMAIL PROTECTED] PR

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-20 Thread manu at gcc dot gnu dot org
--- Comment #11 from manu at gcc dot gnu dot org 2008-08-20 16:38 --- Fixed in GCC 4.4 -- manu at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-11 Thread jakub at gcc dot gnu dot org
--- Comment #9 from jakub at gcc dot gnu dot org 2008-08-11 13:14 --- To answer c#7, that's what would (and does) happen for autoparallelization. But OpenMP is explicit parallelization, if you don't preceede for (...; ...; ...) ... construct with #pragma omp {,parallel } for, nothing

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-10 Thread jakub at gcc dot gnu dot org
--- Comment #4 from jakub at gcc dot gnu dot org 2008-08-10 21:46 --- This is invalid OpenMP code. See 2.5.1 (in OpenMP 3.0, similar wording is in 2.5 standard too): init-expr One of the following: var = lb integer-type var = lb

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-10 Thread danny dot dyk at tu-dortmund dot de
--- Comment #5 from danny dot dyk at tu-dortmund dot de 2008-08-10 22:17 --- That means - contrary to popular knowledge - that OpenMP is not C++ compatible. Fair enough! Just don't announce it as such, then. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35158

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-10 Thread jakub at gcc dot gnu dot org
--- Comment #6 from jakub at gcc dot gnu dot org 2008-08-10 22:28 --- No idea how do you infer that from this. If you use #pragma omp for before a loop construct, there are many restrictions you need to honor to have a valid OpenMP program, this is just one of them. To list just some

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-10 Thread danny dot dyk at tu-dortmund dot de
--- 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

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-10 Thread manu at gcc dot gnu dot org
--- Comment #8 from manu at gcc dot gnu dot org 2008-08-10 22:50 --- A patch was posted here: http://gcc.gnu.org/ml/gcc-patches/2008-08/msg00442.html (I miss the patch tracker!!!) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35158

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-06 Thread manu at gcc dot gnu dot org
--- Comment #2 from manu at gcc dot gnu dot org 2008-08-06 20:14 --- Reconfirmed in GCC 4.4 -- manu at gcc dot gnu dot org changed: What|Removed |Added Known to

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-08-06 Thread manu at gcc dot gnu dot org
--- Comment #3 from manu at gcc dot gnu dot org 2008-08-06 22:26 --- CC Jakub, Is this initialization allowed in OpenMP or not? I have a patch that handles it, so we can either allow it or we can give an error such: error: parenthesized initialization not allowed in OpenMP ‘for’ --

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

2008-02-13 Thread manu at gcc dot gnu dot org
--- Comment #1 from manu at gcc dot gnu dot org 2008-02-13 22:10 --- Confirmed in GCC 4.3 revision 132291. -- manu at gcc dot gnu dot org changed: What|Removed |Added