*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowWhat is Microlib?
Applies to: Libraries, RealView Development Suite (RVDS) 3.1

In RVDS 3.1 a new C library called micro-library (Microlib) is introduced.  Microlib is highly optimized for small code size. It is targeted to be used in deeply embedded applications where memory resources are limited. To minimize code size, it has less functionality than the default standard C library. Some library functions will also be slower, for example, memcpy().

The main feature of Microlib is its small footprint. For example, the simple “Hello World” project built with Microlib only contains 260 bytes of ARM code, comparing to 7.4KB when built with standard C library.

Microlib is not designed to interoperate with the C++ library. It does not provide all the support functions which C++ code can invoke, e.g., exceptions and RTTI. Some other parts of the C++ run-time library may also depend on functions defined by the standard library but not by Microlib.



Related:






back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow