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/49581] New: [trans-mem] save/restore of thread-local data in nested txns is missing
Date: Wed, 29 Jun 2011 15:52:00 -0000 [thread overview]
Message-ID: <bug-49581-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49581
Summary: [trans-mem] save/restore of thread-local data in
nested txns is missing
Product: gcc
Version: trans-mem
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: torvald@gcc.gnu.org
Created attachment 24632
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24632
test case
In the attached test case, stores to x[5] and x[6] in the nested txn do not get
rolled back. This happens if the nested txn is restarted by the TM runtime
library, or if the nested txn is aborted via __transaction_cancel.
next reply other threads:[~2011-06-29 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 15:52 torvald at gcc dot gnu.org [this message]
2012-01-11 15:36 ` [Bug c/49581] " aldyh at gcc dot gnu.org
2012-01-11 17:24 ` aldyh at gcc dot gnu.org
2012-01-31 13:27 ` torvald 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-49581-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).