OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clarify ABI requirements for data-logging functions. 

* libitm.texi: Clarify ABI requirements for data-logging functions.

From-SVN: r192778
This commit is contained in:
Torvald Riegel 2012-10-24 19:52:18 +00:00 committed by Torvald Riegel
parent b679c81340
commit eb00e95920
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
libitm/ChangeLog
View File

@ -1,3 +1,7 @@
2012-10-24 Torvald Riegel <triegel@redhat.com>
* libitm.texi: Clarify ABI requirements for data-logging functions.
2012-10-24 Torvald Riegel <triegel@redhat.com>
* retry.cc (gtm_thread::decide_begin_dispatch): Ask dispatch whether

7
libitm/libitm.texi
View File

@ -156,6 +156,13 @@ about which memory locations are shared and which are not shared with other
threads (i.e., data must be accessed either transactionally or
nontransactionally). Otherwise, non-write-through TM algorithms would not work.
For memory locations on the stack, this requirement extends to only the
lifetime of the stack frame that the memory location belongs to (or the
lifetime of the transaction, whichever is shorter). Thus, memory that is
reused for several stack frames could be target of both data logging and
transactional accesses; however, this is harmless because these stack frames'
lifetimes will end before the transaction finishes.
@subsection [No changes] Scatter/gather calls
@subsection [No changes] Serial and irrevocable mode
@subsection [No changes] Transaction descriptor