[PATCH, newlib] Allow locking routine to be retargeted

Thomas Preudhomme thomas.preudhomme@foss.arm.com
Wed Dec 14 14:36:00 GMT 2016



On 14/12/16 14:21, Sebastian Huber wrote:
>
>
> On 13/12/16 18:18, Thomas Preudhomme wrote:
>> +#else
>> +
>> +typedef void * _LOCK_T;
>> +#define _LOCK_RECURSIVE_T _LOCK_T
>> +
>> +#define __LOCK_INIT(class,lock) extern struct_lock _lock_  ## lock; \
>> +    class_LOCK_T lock = &_lock_  ## lock
>> +#define __LOCK_INIT_RECURSIVE(class,lock) __LOCK_INIT(class,lock)
>
> I would use:
>
> struct _lock;
> typedef struct _lock *_LOCK_T;
>
> This makes debugging a bit easier.

But then if your lock is just an integer you have to use a structure with a 
single field, right?

Why is struct _lock easier to debug by the way?

Best regards,

Thomas



More information about the Newlib mailing list