diff options
author | marcus <marcus> | 2003-09-13 00:25:50 +0000 |
---|---|---|
committer | marcus <marcus> | 2003-09-13 00:25:50 +0000 |
commit | db3bd625f20de535bcab489d39acfe635f7bd595 (patch) | |
tree | 5790e5b05982a69e2b1e62880ddf856b56e9b14b /libc-parts/README | |
parent | 1c19688db671548ef174497f7c6507773ba48221 (diff) |
Add libc-parts, which takes functions out of libc.a bit by bit.
Diffstat (limited to 'libc-parts/README')
-rw-r--r-- | libc-parts/README | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/libc-parts/README b/libc-parts/README new file mode 100644 index 0000000..2ee60e9 --- /dev/null +++ b/libc-parts/README @@ -0,0 +1,20 @@ +libc-parts +========== + +libc-parts is a convenience library that is built by taking functions +from the statically linked GNU C library of the host system. + +Even if you can not link to the whole of the C library, you can often +link to specific functions to it, which don't have a lot of +dependencies. This includes memory and string operations, as well as +many other low level operations (byte swap routines, bit search +functions, etc). + +These functions are usually cleverly optimized for the host processor, +and well tested. So taking the standard implementations gives best +over-all performance, avoids code duplications, and is the least error +prone solution. + +There is obviously a boot strap issue in this approach. However, this +is not a serious problem as the functions are not OS dependent, and +thus any static GNU C library for the host CPU will do. |