public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "per at bitempire dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/40494]  New: omp for loop with guided schedule fails to terminate in certain cases
Date: Fri, 19 Jun 2009 16:47:00 -0000	[thread overview]
Message-ID: <bug-40494-17858@http.gcc.gnu.org/bugzilla/> (raw)

The following loop, which seems valid according to the OpenMP specification
v2.5 and 3.0 fails to terminate:

int x;
#pragma omp parallel for schedule(guided)
for(x = 3; x < 478; x += 2) {
  ...
}

I've tested with two and eight threads and different chunksizes, with the same
non-termination result. Changing the upper bound to 477, however, makes the
loop terminate, which leads me to belive this is an issue in the GNU OpenMP
runtime library.

I have confirmed that the problems exists in 4.2, 4.3 and 4.5 (trunk,
19-06-09). To me,  bug 35625 seems somewhat similar but was supposedly fixed in
4.3.

/Per


-- 
           Summary: omp for loop with guided schedule fails to terminate in
                    certain cases
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: per at bitempire dot com
 GCC build triplet: i686-pc-linux
  GCC host triplet: i686-pc-linux
GCC target triplet: i686-pc-linux


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


             reply	other threads:[~2009-06-19 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 16:47 per at bitempire dot com [this message]
2009-07-10 10:43 ` [Bug libgomp/40494] " jakub at gcc dot gnu dot org
2009-07-28 11:23 ` per at bitempire 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=bug-40494-17858@http.gcc.gnu.org/bugzilla/ \
    --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).