Ah! I finally have a progress bar that doesn't stall the build!
- pipe size in Linux is only 8*512=4096 bytes
- pipe size is not setable
- when the feeding process spits out data faster than the eating
process can read it, then the feeding process stalls after 4KiB
of data sent to the pipe
- for us, the progress bar would spawn a sub-shell every line,
and the sub-shell would in turn spawn a 'date' command.
Which was sloooww as hell, and would cause some kind of a
starvation: the pipe was full most of the time, and the
feeding process was stalled all this time.

Now, we use internal variables and a little hack based onan offset
to determine the elapsed time. Much faster this way, but still
CPU-intensive.

See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10331

and http://gcc.gnu.org/ml/gcc-patches/2003-06/msg00423.html

--- gcc-3.3/gcc/config/sh/t-linux.old	Wed Jun  4 13:01:39 2003

+++ gcc-3.3/gcc/config/sh/t-linux	Wed Jun  4 13:02:12 2003

@@ -1,3 +1,6 @@

+# Don't run fixproto

+STMP_FIXPROTO =

+

 TARGET_LIBGCC2_CFLAGS = -fpic

 LIB1ASMFUNCS_CACHE = _ic_invalidate