gomp - equivalence for threadprivate data

[Steve Kargl]

On Mon, Jan 26, 2009 at 07:52:05PM +0100, Tobias Burnus wrote:
> 
> Steve Kargl wrote:
> > <rant>
> > Gfortran (and OpenMP) should not be turned into a cess pool 
> > of numerable many options because people are too lazy to 
> > fix their code.  What's the point in having Standards and
> > writing compilers that conform to those Standard, if gfortran
> > continually provides options to violate those Standards.
> > </rant>

(snip)

> For the specific problem: Given that most (all?) other OpenMP compiler
> support it, I think it would be useful to accept it as well. However, I
> think having either an overrideable error message (-fopenmp-std=legacy
> or similar) - or a default-enabled warning - should be used.

I doubt that this misfeature has ever been allowed by any 
revision of the OpenMPi Standard, so -fopen-std=legacy make
no sense.  Perhaps, -fopenmp-lemming or -fgnu-openmp.  The
default behavior should be an error.

> Regarding the legacy checking: Gfortran also supports the <tab>
> character in $omp! contrary to the standard but in line with the other
> compilers. One could add an error/warning there, but again one misses a
> -fopenmp-std= option.

tab is perfectly fine within OpenMP 3.0.

>From OpenMP 3.0,

   white space   A non-empty sequence of space and/or horizontal
                 tab characters.

For fixed form code:

   Fortran fixed form line length, white space, continuation, and column
   rules apply to the directive line.

For free form code:

   The sentinel can appear in any column as long as it is preceded only
   by white space (spaces and tab characters).

-- 
Steve