public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement
@ 2010-11-25 9:03 patrick.marlier at gmail dot com
2010-11-25 9:04 ` [Bug c++/46654] " patrick.marlier at gmail dot com
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: patrick.marlier at gmail dot com @ 2010-11-25 9:03 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug c++/46654] [trans-mem] "volatile" objects must not be allowed in a safe statement 2010-11-25 9:03 [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement patrick.marlier at gmail dot com @ 2010-11-25 9:04 ` patrick.marlier at gmail dot com 2010-11-25 9:39 ` patrick.marlier at gmail dot com ` (3 subsequent siblings) 4 siblings, 0 replies; 6+ messages in thread From: patrick.marlier at gmail dot com @ 2010-11-25 9:04 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46654 --- Comment #1 from Patrick Marlier <patrick.marlier at gmail dot com> 2010-11-25 08:58:10 UTC --- Created attachment 22525 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22525 testcase with volatile in transaction. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/46654] [trans-mem] "volatile" objects must not be allowed in a safe statement 2010-11-25 9:03 [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement patrick.marlier at gmail dot com 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 ` (2 subsequent siblings) 4 siblings, 0 replies; 6+ messages in thread From: patrick.marlier at gmail dot com @ 2010-11-25 9:39 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46654 Patrick Marlier <patrick.marlier at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |trans-mem Severity|normal |enhancement ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/46654] [trans-mem] "volatile" objects must not be allowed in a safe statement 2010-11-25 9:03 [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement patrick.marlier at gmail dot com 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 4 siblings, 0 replies; 6+ messages in thread From: aldyh at gcc dot gnu.org @ 2010-12-13 11:13 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46654 Aldy Hernandez <aldyh at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P5 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/46654] [trans-mem] "volatile" objects must not be allowed in a safe statement 2010-11-25 9:03 [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement patrick.marlier at gmail dot com ` (2 preceding siblings ...) 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 4 siblings, 0 replies; 6+ messages in thread From: aldyh at gcc dot gnu.org @ 2010-12-14 16:41 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46654 Aldy Hernandez <aldyh at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2010.12.14 16:41:22 Ever Confirmed|0 |1 --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> 2010-12-14 16:41:22 UTC --- Fixed and awaiting approval: http://gcc.gnu.org/ml/gcc-patches/2010-12/msg01103.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug c++/46654] [trans-mem] "volatile" objects must not be allowed in a safe statement 2010-11-25 9:03 [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement patrick.marlier at gmail dot com ` (3 preceding siblings ...) 2010-12-14 16:41 ` aldyh at gcc dot gnu.org @ 2010-12-20 18:22 ` aldyh at gcc dot gnu.org 4 siblings, 0 replies; 6+ messages in thread From: aldyh at gcc dot gnu.org @ 2010-12-20 18:22 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46654 Aldy Hernandez <aldyh at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |FIXED ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-12-20 18:22 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-11-25 9:03 [Bug c++/46654] New: [trans-mem] "volatile" objects must not be allowed in a safe statement patrick.marlier at gmail dot com 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
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).