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.

 --- /dev/null	Sat Dec 14 13:56:51 2002

 +++ gcc-3.3.1/gcc/testsuite/gcc.dg/pr10589-1.c	Mon Sep 15 08:57:58 2003

 @@ -0,0 +1,14 @@

 +/* PR target/10589

 + * Reporter: mathieu@thenesis.com

 + * Summary: For Hitachi SH target, GCC crashes when both -fomit-frame-pointer and -mdalign options are specified

 + * Keywords: ice-on-valid-code

 + * Testcase by Kazu Hirata, tweaked by dank@kegel.com

 + * Did not fail in Hard Hat 2.0 gcc-2.97, nor in dodes gcc-3.0.2, so this is a regression, so I'm not marking it xfail

 + */

 +/* { dg-do compile { target sh*-*-* } } */

 +/* { dg-options "-fomit-frame-pointer -mdalign" } */

 +

 +int foo(int a, int b)

 +{

 +	return a / b;

 +}