gomp - equivalence for threadprivate data
Matevz Tadel
matevz.tadel@cern.ch
Tue Jan 27 12:24:00 GMT 2009
Tobias Burnus wrote:
> Tim Prince wrote:
>>>> I've attached a cut-down example of the way a well-known legacy
>>>> application violates OpenMP standard.
>>>>
>>> I had do add something like [...]
>>>
>> I cut out too many COMMON blocks. Those arrays were declared in
>> additional labeled COMMON blocks, set as threadprivate.
>> The Sun, Intel, and PGI compilers are used in production for this application.
>>
> And as written, it also works with the Pathscale compiler and the free
> Open64 compiler, i.e. of my 6 OpenMP supporting compilers, only gfortran
> rejects it.
>
> I filled a bugreport (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38979)
> to track this.
First, thank you all for taking interest in this.
Tobias wrote in the comment to the bug report that simply removing the error
might already be enough.
If you can point us to the place where this error is generated we can test if
disabling it (or changing it to a warning) produces the desired results.
Matevz
<snip>
More information about the Fortran
mailing list