[Bug fortran/40876] OpenMP private variable referenced in a statement function

2020-10-26 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876

Bill Long  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|REOPENED

--- Comment #11 from Bill Long  ---
With 10.2.0 there is still no error message for the invalid use of A in a
private() clause of the OpenMP directive.

[Bug fortran/40876] OpenMP private variable referenced in a statement function

2015-12-05 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876

Dominique d'Humieres  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #10 from Dominique d'Humieres  ---
> Relate to/duplicate of pr38724?

Marked as duplicate of pr38724.

*** This bug has been marked as a duplicate of bug 38724 ***

[Bug fortran/40876] OpenMP private variable referenced in a statement function

2015-11-03 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876

Dominique d'Humieres  changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #9 from Dominique d'Humieres  ---
Relate to/duplicate of pr38724?

[Bug fortran/40876] OpenMP private variable referenced in a statement function

2010-12-26 Thread dfranke at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876

Daniel Franke dfranke at gcc dot gnu.org changed:

   What|Removed |Added

 Status|WAITING |NEW
 CC||dfranke at gcc dot gnu.org


[Bug fortran/40876] OpenMP private variable referenced in a statement function

2010-12-26 Thread longb at cray dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876

--- Comment #8 from Bill Long longb at cray dot com 2010-12-27 01:42:20 UTC 
---
I am out of the office until Monday, January 3, 2011.  Send technical questions
to spsl...@cray.com.


[Bug fortran/40876] OpenMP private variable referenced in a statement function

2010-05-07 Thread dfranke at gcc dot gnu dot org


--- Comment #6 from dfranke at gcc dot gnu dot org  2010-05-07 19:50 ---
(In reply to comment #5)
 I tried 4.4.2 and do not any longer see the segfault on the Cray XT system.

This PR can thus be closed?


-- 

dfranke at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876



[Bug fortran/40876] OpenMP private variable referenced in a statement function

2010-05-07 Thread longb at cray dot com


--- Comment #7 from longb at cray dot com  2010-05-07 22:06 ---
The original problem reported in the Description concerned a missing error
message.  So, fixing the segfault (while an excellent situation) does not
address the original issue.  My 2 cents is this is not ready to close yet.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876



[Bug fortran/40876] OpenMP private variable referenced in a statement function

2009-11-13 Thread longb at cray dot com


--- Comment #5 from longb at cray dot com  2009-11-13 22:19 ---
I tried 4.4.2 and do not any longer see the segfault on the Cray XT system.  I
suspect this was fixed by addressing the problem noted in Comment #3. 

The original problem of not issuing the error message at compile time remains.
This (correct) comment in Comment #5:

---
However, I somehow read the standard differently such that already the
PRIVATE(J) is invalid.
---

focuses on the actual issue.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876



[Bug fortran/40876] OpenMP private variable referenced in a statement function

2009-07-28 Thread jakub at gcc dot gnu dot org


--- Comment #1 from jakub at gcc dot gnu dot org  2009-07-28 12:20 ---
I certainly can't reproduce any kind of segfault with this.
And, it is unclear to me whether this restriction (why it is there at all,
doesn't make much sense) is meant just for statement functions referenced
within the omp region, or any.  Say is:
integer :: a, st_func
st_func () = a
!$omp parallel private (a)
a = 1
!$omp end parallel
end
also supposed to be invalid?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876




[Bug fortran/40876] OpenMP private variable referenced in a statement function

2009-07-28 Thread longb at cray dot com


--- Comment #2 from longb at cray dot com  2009-07-28 13:47 ---
The text at [75:19-20] of the OpenMP 2.5 standard, May 2008, says:

Variables that appear in namelist statements, in variable format expressions,
and in Fortran expressions for statement function definitions, may not appear
in a private clause.

So the example in Comment #1 looks invalid.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876



[Bug fortran/40876] OpenMP private variable referenced in a statement function

2009-07-28 Thread jv244 at cam dot ac dot uk


--- Comment #3 from jv244 at cam dot ac dot uk  2009-07-28 14:34 ---
(In reply to comment #1)
 I certainly can't reproduce any kind of segfault with this.

It could be that it segfaults for Bill because 'ftn' adds -static to the
compiler options, but doesn't link libpthread with '-Wl,--whole-archive
-lpthread -Wl,--no-whole-archive' (see PR39176). Certainly, this happened in
the past on the XT5. It is something Bill could check on the Cray :-)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876



[Bug fortran/40876] OpenMP private variable referenced in a statement function

2009-07-28 Thread burnus at gcc dot gnu dot org


--- Comment #4 from burnus at gcc dot gnu dot org  2009-07-28 14:43 ---
(In reply to comment #1)
 I certainly can't reproduce any kind of segfault with this.

Neither can I.  Regarding both examples (comment 0 and comment 1), ifort 11.1
happily accepts both.

I am not sure whether it is the correct interpretation according the standard,
but
http://publib.boulder.ibm.com/infocenter/lnxpcomp/v9v111/topic/com.ibm.xlf111.linux.doc/xlfopg/smpdirclauses.htm
has:


The following example demonstrates the proper use of a PRIVATE variable that
is used to define a statement function. A commented line shows the invalid use.
Since J appears in a statement function, the statement function cannot be
referenced within the parallel construct for which J is PRIVATE.

  INTEGER :: ARR(10), J = 17
  ISTFNC() = J

!$OMP PARALLEL DO PRIVATE(J)
  DO I = 1, 10
 J=I
 ARR(I) = J
  !  ARR(I) = ISTFNC() **ERROR**   A reference to ISTFNC would
   ! make the PRIVATE(J) clause
   ! invalid.
  END DO
  PRINT *, ARR
  END


However, I somehow read the standard differently such that already the
PRIVATE(J) is invalid.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876



[Bug fortran/40876] OpenMP private variable referenced in a statement function

2009-07-27 Thread jakub at gcc dot gnu dot org


-- 

jakub at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |jakub at gcc dot gnu dot org
   |dot org |
 Status|UNCONFIRMED |ASSIGNED
 Ever Confirmed|0   |1
   Keywords||openmp
   Last reconfirmed|-00-00 00:00:00 |2009-07-27 22:47:35
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40876