public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "torvald at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54893] unable to access volatile variable within relaxed transaction
Date: Thu, 11 Oct 2012 19:54:00 -0000	[thread overview]
Message-ID: <bug-54893-4-7DFboAhgf8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54893-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from torvald at gcc dot gnu.org 2012-10-11 19:54:11 UTC ---
I agree with Michael.  Accesses to volative vars are disallowed in safe code,
but relaxed transactions can run unsafe code (after going irrevocable).  The
test case in bug 46654 is an atomic transaction.


  parent reply	other threads:[~2012-10-11 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 17:46 [Bug c++/54893] New: " spear at cse dot lehigh.edu
2012-10-11 10:41 ` [Bug c++/54893] " aldyh at gcc dot gnu.org
2012-10-11 13:21 ` spear at cse dot lehigh.edu
2012-10-11 19:54 ` torvald at gcc dot gnu.org [this message]
2012-10-11 20:29 ` aldyh at gcc dot gnu.org
2012-10-17 21:18 ` [Bug middle-end/54893] " aldyh at gcc dot gnu.org
2012-10-17 21:19 ` aldyh 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-54893-4-7DFboAhgf8@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).