public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nmm1 at cam dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57618] New: OpenMP atomic read and write are not sequentially consistent
Date: Fri, 14 Jun 2013 21:23:00 -0000	[thread overview]
Message-ID: <bug-57618-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57618
           Summary: OpenMP atomic read and write are not sequentially
                    consistent
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nmm1 at cam dot ac.uk

See bug 57617 for the data and more description.  But the same program
finds that OpenMP atomic read and write are not sequentially consistent.
That will assuredly cause wrong answers when yer everage programmer
attempts to use them.

But should they be?  If you can decode any specification on this matter
from what OpenMP are pleased to call a standard, you are more intelligent
than I am.

So is this a bug, a gotcha or a feature?


             reply	other threads:[~2013-06-14 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 21:23 nmm1 at cam dot ac.uk [this message]
2013-06-15  7:37 ` [Bug c++/57618] " jakub at gcc dot gnu.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=bug-57618-4@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).