public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick.marlier at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement
Date: Thu, 25 Nov 2010 09:03:00 -0000 [thread overview]
Message-ID: <bug-46654-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46654
Summary: [trans-mem] "volatile" objects must not be allowed in
a safe statement
Product: gcc
Version: trans-mem
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: patrick.marlier@gmail.com
CC: rth@gcc.gnu.org, aldyh@gcc.gnu.org
In the Draft transactional construct for C++, "volatile" object are not allowed
in a safe statement (section 3.2). In the current implementation, there is no
warning or error raised by the compiler.
gcc -Wall -c -fgnu-tm volatile.c -o volatile
-> No error
Attached the testcase.
Patrick Marlier.
next reply other threads:[~2010-11-25 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 9:03 patrick.marlier at gmail dot com [this message]
2010-11-25 9:04 ` [Bug c++/46654] " patrick.marlier at gmail dot com
2010-11-25 9:39 ` patrick.marlier at gmail dot com
2010-12-13 11:13 ` aldyh at gcc dot gnu.org
2010-12-14 16:41 ` aldyh at gcc dot gnu.org
2010-12-20 18:22 ` 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-46654-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).