This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH, newlib] Allow locking routine to be retargeted


On Fri, 2016-11-11 at 13:40 +0000, Thomas Preudhomme wrote:
> Right, I didn't think of extra features. The one thing I could think
> of would be 
> to remove usage of the static initializers and only use the function
> initializer 
> which could do a malloc if needed. The issue you described with
> malloc can be 
> avoided by redefining malloc_lock so as not to call the generic lock
> function.
> 
> Now whether this is worth the trouble is another issue because that
> would 
> require more work. Thanks a lot for the feedback, I'm glad you
> pointed out the 
> pitfalls in that approach. It is time to go back to the drawing
> board.

See my earlier message to onkel.jack - I've given some alternative
options there at the end, the one you mentioned is also there. It has a
major problem, that it's not easily possible to actually execute these
initialization functions for most of the global locks...

https://sourceware.org/ml/newlib/2016/msg01093.html

Regards,
FCh


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]