Re: [PATCH v2 05/11] Remove __sinit_locks / __sinit_recursive_mutex
Sebastian Huber <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <[email protected]> |
On 12/05/2022 15:25, Torbjorn SVENSSON via Newlib wrote: > What about the retargetable locking scheme? > Should the mutex __sinit_recursive_mutex be removed from newlib/libc/misc/lock.c too? Yes, we should this dummy mutex. > Without removing the mutex, I suppose there would be a mutex that is never used in the system. > Removing the mutex would pose an API break as I assume that the functions defined in newlib/libc/include/sys/lock.h (and implemented in newlib/libc/misc/lock.c) are to be considered API as it's the functions that the application needs to provide in order to ensure newlib is thread safe. It shouldn't hurt if a lock implementer provides an unused mutex. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: [email protected] phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08 Registergericht: Amtsgericht München Registernummer: HRB 157899 Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler Unsere Datenschutzerklärung finden Sie hier: https://embedded-brains.de/datenschutzerklaerung/