crosstool-ng: patches/gcc/3.3.2/empty6.patch@ea15433daba0

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.

     1 From 3.4 branch.  Fixes test failure

     2 FAIL: g++.dg/abi/empty6.C  (test for warnings, line 6)

     4 ===================================================================

     5 RCS file: /cvs/gcc/gcc/gcc/testsuite/g++.dg/abi/empty6.C,v

     6 retrieving revision 1.1

     7 retrieving revision 1.2

     8 diff -u -r1.1 -r1.2

     9 --- gcc/gcc/testsuite/g++.dg/abi/empty6.C	2002/09/25 19:07:35	1.1

    10 +++ gcc/gcc/testsuite/g++.dg/abi/empty6.C	2003/06/03 19:10:09	1.2

    11 @@ -5,4 +5,9 @@

    12  struct B {

    13    A a; // { dg-warning "empty" }

    14    virtual void f () {}

    15 -};

    16 +} __attribute__((aligned(8)));

    17 +/* The preceding attribute is necessary on targets with

    18 +   BIGGEST_ALIGNMENT <= 32 to trigger the warning, as otherwise a 32 bit

    19 +   offset is split into DECL_FIELD_OFFSET 4 and DECL_FIELD_BIT_OFFSET 0,

    20 +   and then there is no discrepancy between DECL_FIELD_OFFSET and

    21 +   byte_position to warn about.  */

author	"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
	Sun May 20 13:48:26 2007 +0000 (2007-05-20)
changeset 112	ea15433daba0
permissions	-rw-r--r--