> (nil if no %[efg] routines loaded, so don't call them). It seemed to > me to be a simple and elegant hack that we could revive if the space > consumption really matters.
It's not clear that floating point print routines are worth singling out any more. Here's a list of all the library object files with multiple copies occupying cumulatively more than 100000 bytes of text space in commands in /386/bin. The three columns of numbers are #copies, text size, and cumulative text size. 132 787 103884 /sys/src/libc/9sys/convM2D.c 60 1738 104280 /sys/src/libc/9sys/qlock.c 32 3302 105664 /sys/src/libc/9sys/fcallfmt.c 13 9070 117910 /sys/src/lib9p/srv.c 209 600 125400 /sys/src/libc/port/frexp.c 7 18078 126546 /sys/src/libsec/port/x509.c 31 4830 149730 /sys/src/libdraw/init.c 7 22109 154763 /sys/src/libsec/port/tlshand.c 7 22626 158382 /sys/src/libmemdraw/draw.c 209 805 168245 /sys/src/libc/fmt/fmt.c 189 1598 302022 /sys/src/libc/port/malloc.c 209 2453 512677 /sys/src/libc/fmt/fltfmt.c 209 3006 628254 /sys/src/libc/port/strtod.c 209 3888 812592 /sys/src/libc/386/vlrt.c 209 5078 1061302 /sys/src/libc/fmt/dofmt.c 189 9957 1881873 /sys/src/libc/port/pool.c If I was looking for ways to reduce space I would probably start with vlrt.c and pool.c -- Richard
