mirror of
https://gcc.gnu.org/git/gcc.git
synced 2024-11-23 19:03:59 +08:00
Clarify ABI requirements for data-logging functions.
* libitm.texi: Clarify ABI requirements for data-logging functions. From-SVN: r192778
This commit is contained in:
parent
b679c81340
commit
eb00e95920
@ -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
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user