public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32551] incorrect output obtained from nested parallelism that is serialized
Date: Fri, 29 Jun 2007 21:28:00 -0000 [thread overview]
Message-ID: <20070629212811.31694.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32551-14710@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from dfranke at gcc dot gnu dot org 2007-06-29 21:28 -------
Seems to be fixed in trunk:
$> gfortran-svn -g -Wall -fopenmp pr32551.f90 && ./a.out
omp_get_nested()= F
2 2 2 2
$> gfortran-svn -v
gcc version 4.3.0 20070628 (experimental)
As I am not 100% sure whether I fully understand your testcase (e.g. why expect
2 as a result, not somethinig from 2-5, depending on the thread hitting the
innermost parallel-region first?), I won't close it yet. Maybe Jakub has
something to say on this?!
--
dfranke at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dfranke at gcc dot gnu dot
| |org, jakub at gcc dot gnu
| |dot org
GCC build triplet|x86_64-suse-linux |
GCC host triplet|x86_64-suse-linux |
GCC target triplet|x86_64-suse-linux |
Keywords| |openmp
Summary|INCORRECT OUTPUT OBTAINED |incorrect output obtained
|FROM NESTED PARALLELISM THAT|from nested parallelism that
|IS SERIALIZED |is serialized
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32551
next prev parent reply other threads:[~2007-06-29 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 18:58 [Bug fortran/32551] New: INCORRECT OUTPUT OBTAINED FROM NESTED PARALLELISM THAT IS SERIALIZED longb at cray dot com
2007-06-29 21:28 ` dfranke at gcc dot gnu dot org [this message]
2007-07-02 12:04 ` [Bug fortran/32551] incorrect output obtained from nested parallelism that is serialized jakub at gcc dot gnu dot org
2007-07-02 12:05 ` jakub at gcc dot gnu dot org
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=20070629212811.31694.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).