Thread safety in the Arm® C library
Arm® C library functions are either always thread-safe, never thread-safe, or thread-safe in certain circumstances.
In the Arm C library:
Some functions are never thread-safe, for example
Some functions are inherently thread-safe, for example
Some functions, such as
malloc(), can be made thread-safe by implementing the
Other functions are only thread-safe if you pass the appropriate arguments, for example
Threading problems might occur when your application makes use of the Arm C library in a way that is hidden, for example, if the compiler implicitly calls functions that you have not explicitly called in your source code. Familiarity with the thread-safe C library functions and C library functions that are not thread-safe can help you to avoid this type of threading problem, although in general, it is unlikely to arise.