diff options
| author | rpj <rpj> | 2002-02-02 23:15:28 +0000 |
|---|---|---|
| committer | rpj <rpj> | 2002-02-02 23:15:28 +0000 |
| commit | 4a72430d821b96add23846980d07f5a01059029d (patch) | |
| tree | 6601b116e591db28feaed15a92ae46bfed8197da /README.NONPORTABLE | |
| parent | 6a65a568fa4d9515265842c8bcf11a7449f3c325 (diff) | |
* cancel.c: Rearranged some code and introduced checks
to disable cancelation at the start of a thread's cancelation
run to prevent double cancelation. The main problem
arises if a thread is canceling and then receives a subsequent
async cancel request.
* private.c: Likewise.
* condvar.c: Place pragmas around cleanup_push/pop to turn
off inline optimisation (/Obn where n>0 - MSVC only). Various
optimisation switches in MSVC turn this on, which interferes with
the way that cleanup handlers are run in C++ EH and SEH
code. Application code compiled with inline optimisation must
also wrap cleanup_push/pop blocks with the pragmas, e.g.
#pragma inline_depth(0)
pthread_cleanup_push(...)
...
pthread_cleanup_pop(...)
#pragma inline_depth(8)
* rwlock.c: Likewise.
* mutex.c: Remove attempts to inline some functions.
* signal.c: Modify misleading comment.
tests/
* mutex8: New test.
* mutex8n: New test.
* mutex8e: New test.
* mutex8r: New test.
* cancel6a: New test.
* cancel6d: New test.
* cleanup0.c: Add pragmas for inline optimisation control.
* cleanup1.c: Add pragmas for inline optimisation control.
* cleanup2.c: Add pragmas for inline optimisation control.
* cleanup3.c: Add pragmas for inline optimisation control.
* condvar7.c: Add pragmas for inline optimisation control.
* condvar8.c: Add pragmas for inline optimisation control.
* condvar9.c: Add pragmas for inline optimisation control.
Diffstat (limited to 'README.NONPORTABLE')
| -rw-r--r-- | README.NONPORTABLE | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/README.NONPORTABLE b/README.NONPORTABLE index a4e21f3..b6e6768 100644 --- a/README.NONPORTABLE +++ b/README.NONPORTABLE @@ -65,9 +65,9 @@ int pthread_num_processors_np This routine (found on HPUX systems) returns the number of processors - in the system. This implementations actually returns the number of - processors available to the process, which can be a different (lower) - value depending on the process's affinity mask. + in the system. This implementation actually returns the number of + processors available to the process, which can be a lower number + than the system's number, depending on the process's affinity mask. BOOL pthread_win32_process_attach_np (void); |