| To: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Defect in XBD XBD 4.10 |
| From: | Alexander Terekhov <yyyyyyyy@xxxxxxxxxx> |
| Date: | Sat, 6 Nov 2004 21:40:42 +0100 |
> ---- > Applications shall ensure that access to any memory location by more > than one thread is restricted such that no thread can read or modify > a memory location while another thread of control may be modifying it. > Applications shall use functions listed below that synchronize thread > execution and ensure that modifications to locations in memory are > ordered with respect to accesses to the same memory locations in other > threads. There is a happens-before inter-thread ordering with respect > to preceding (in program and inter-thread order) modifications of > memory locations in ... I forgot XSI IPC semas and pthread_once(). Semas aside for a moment, ---- a thread calling pthread_once() and on a specified pthread_once_t object returning from a specified init_routine and accesses to modified memory locations in another thread after another thread returns from pthread_once() on the same pthread_once_t object. ---- Well, yeah, my English sucks, I just hope that you can undertand what I mean and we'll end up with some proper wording. ;-) regards, alexander. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Defect in XBD XBD 4.10, terekhov |
|---|---|
| Next by Date: | Defect in XBD 4.10 Memory Synchronization [read-write locking], terekhov |
| Previous by Thread: | Defect in XBD XBD 4.10, terekhov |
| Next by Thread: | Defect in XBD 4.10 Memory Synchronization [read-write locking], terekhov |
| Indexes: | [Date] [Thread] [All Lists] |