Lines Matching +full:- +full:a

3 When newlib-multithread and newlib-retargetable-locking are enabled,
6 that a single-threaded application can still use a Picolibc compiled
7 with locking enabled. An application needing locking must provide a
12 Picolibc has a single global lock for APIs that share global
21 Tinystdio (the default stdio) uses per-file locks for the buffered
26 The legacy stdio implementation is full of locking, and has per-file
33  * newlib-retargetable-locking. When 'true', locking operations are
36  * newlib-multithread. When 'true', the library is built with
40 interrelated as to make them effectively co-dependent, so users must
45 When newlib-multithread and newlib-retargetable-locking are enabled
47 stubs for all of these functions that do not perform locking, so a
48 single threaded application can still use a library compiled to enable
49 locking. An application needing locking would provide a real
53 only provides non-recursive mutexes, a suitable wrapper implementing
68 defined in the locking implementation in such a way as to not require
73 This is used by tinystdio to initialize the lock in a newly allocated
78 Acquire a non-recursive mutex. A thread will only acquire the mutex once.
82 Release a non-recursive mutex.
86 This is used by tinystdio to de-initialize a lock from a FILE which is
91 This is used by the legacy stdio code to initialize the lock in a
96 Acquire a recursive mutex. A thread may acquire a recursive
101 Release a recursive mutex. A thread thread must release the mutex as
106 This is used by the legacy stdio code to de-initialize a lock from a