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] |
One thing to keep in mind is that many of these other libc implementations are far from complete. They implement a small subset of capabilities.
Newlib aims for high compatibility with standards while still being suitable for use in embedded systems.
As you note, avr-libc focuses heavily on AVRs with little (no?) concern for other CPU architectures. My recollection is that it also is a libc subset. Different project goal.
Corinna's to lower the buffer size or move the routine so it isn't inlined would on a first order pass both be acceptable. It may make sense to do both.
Another design consideration which sometimes comes into play is to limit or forbid malloc()'s after the program completes initialization. The malloc() solution would push against this rule and require analysis to ensure that all paths free the memory. [1]
Cheers, FCh
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |