gomp - equivalence for threadprivate data

[Steve Kargl]

On Mon, Jan 26, 2009 at 08:53:36AM -0800, Tim Prince wrote:
> Tobias Burnus wrote:
> > Tim,
> > 
> > Tim Prince wrote:
> >> We do use ifort and pgf90 to build other applications which
> >> violate OpenMP standard in this respect.
> > Can you give a list/example for widely supported OpenMP violating
> > directives? One could then think of adding support for those in GCC. I
> > have to admit I do not have much knowledge about OpenMP - and none with
> > regards to common OpenMP extensions.
> > 
> > In any case, using
> >    !$omp threadprivate(/GCPARM/, PACUTS)
> > failed here not only with gfortran but also with ifort (9.1 and 11),
> > pathf95 and sunf95; though it compiles with openf95 and with pgf95.
> > 
> > Tobias
> I've attached a cut-down example of the way a well-known legacy
> application violates OpenMP standard.

If you're rewriting code to use OpenMP, one should take the
opportunity to update the code in a conforming manner.

<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>
-- 
Steve