In the ARM C library:
some functions are never thread-safe, for example
setlocale()some functions are inherently thread-safe, for example
memcpy()some functions, such as
malloc(), can be made thread-safe by implementing the_mutex_functions*other functions are only thread-safe if you pass the appropriate arguments, for example
tmpnam().
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.
See also- Tasks
- Concepts
- Reference
ARM C and C++ Libraries and Floating-Point Support Reference:
PDF version