Lines Matching +full:musl +full:- +full:tools

2 <!--#include file="header.html" -->
75 way there, and most of the rest is either fine-tuning or more trouble than
85 <p>Speed is easy to measure; there are dozens of profiling tools for Linux
95 code, encryption, rsync...)  Worry about throughput inside long-running
110 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part1-2.html>part one</a>,
111 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part2-1.html>part two</a>,
112 <a href=http://arstechnica.com/paedia/r/ram_guide/ram_guide.part3-1.html>part three</a>,
116 <a href=http://arstechnica.com/articles/paedia/cpu/bandwidth-latency.ars>bandwidth
124 is 128k and a big L2 cache is a couple of megabytes.  A cheap low-power
127 <p>Learn how <a href=http://nommu.org/memory-faq.txt>virtual memory and
131 operating system to break copy-on-write, which allocates more memory.  (The
133 copy-on-write mappings of the zero page.  Actual physical pages get allocated
134 when the copy-on-write gets broken by writing to the virtual page.  This
199 compilation and linking.  Matt Mackall's bloat-o-meter is a python script
232 <p>Simplicity itself can have subtle non-obvious aspects requiring a tradeoff
251 testing that we work with C libraries which support static linking (musl does,
252 glibc doesn't) is another way to be self-contained with known boundaries:
277 approach (half-minute wait vs instant results). This is one example
283 in knowledge about strange real-world use cases that the designers didn't
287 <p>That said, the Mythical Man-Month's "build one to throw away" advice points
296 Open source software can afford to re-implement code that works, over and
300 versions, Coherent was the first full from-scratch Unix clone in 1980,
302 the GNU tools were yet another rewrite intended for use in the stillborn
315 <a href=http://blog.outer-court.com/archive/2005-08-24-n14.html>why
321 <p>Toybox should run on Android (all commands with musl-libc, as large a subset
329 <p>We depend on C99 and posix-2008 libc features such as the openat() family of
352 x86-64 were <a href=http://www.pagetable.com/?p=6>explicitly designed to
356 guarantees that on any Unix-like platform "long" and "pointer" types
375 curious here are <a href=https://devblogs.microsoft.com/oldnewthing/20050131-00/?p=36563>the insane…
381 feeding the compiler -funsigned-char.</p>
383 <p>The reason to pick "unsigned" is that way char strings are 8-bit clean by
384 default, which makes UTF-8 support easier.</p>
393 <p>Thus "bad -A '%c'" is
394 preferable to "Unrecognized address base '%c'", because a non-english speaker
395 can see that -A was the problem (giving back the command line argument they
404 (which non-english speakers can presumably recognize already). Keep the
412 <p>All commands should be 8-bit clean, with explicit
413 <a href=http://yarchive.net/comp/linux/utf8.html>UTF-8</a> support where
415 it and pass it through. (For this reason, our build is -funsigned-char on
422 <p>Someday we should probably have translated --help text, but that's a
423 post-1.0 issue.</p>
431 <a href=roadmap.html#dev_env>self-hosting development envirionments</a>,
440 deflate and sha1sum, which lets the corresponding built-in implementations
441 be simple (and thus slow). But the built-in implementations need to exist and
459 Just as a GPLv2 project can't incorporate GPLv3 code and a BSD-licensed
484 sed -i ':loop;s/^\( *\)  /\1\t/;t loop' filename
489 sed -i ':loop;s/^\( *\)\t/\1  /;t loop' filename
580 thing as self-documenting code (if nothing else, code with _no_ comments
585 <!--#include file="footer.html" -->