public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40876] OpenMP private variable referenced in a statement function
Date: Tue, 28 Jul 2009 12:21:00 -0000	[thread overview]
Message-ID: <20090728122047.21057.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40876-14710@http.gcc.gnu.org/bugzilla/>



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


  parent reply	other threads:[~2009-07-28 12:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 17:52 [Bug fortran/40876] New: " longb at cray dot com
2009-07-27 22:47 ` [Bug fortran/40876] " jakub at gcc dot gnu dot org
2009-07-28 12:21 ` jakub at gcc dot gnu dot org [this message]
2009-07-28 13:47 ` longb at cray dot com
2009-07-28 14:35 ` jv244 at cam dot ac dot uk
2009-07-28 14:43 ` burnus at gcc dot gnu dot org
2009-11-13 22:20 ` longb at cray dot com
2010-05-07 19:50 ` dfranke at gcc dot gnu dot org
2010-05-07 22:06 ` longb at cray dot com
     [not found] <bug-40876-4@http.gcc.gnu.org/bugzilla/>
2010-12-27  1:40 ` dfranke at gcc dot gnu.org
2010-12-27  1:42 ` longb at cray dot com
2020-10-26 15:57 ` longb at cray dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090728122047.21057.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).