Measuring alignment
Andreas Jaeger
aj@suse.de
Thu Mar 30 09:23:00 GMT 2000
Hi Richard,
here're the results from make check after applying all of your patches:
FAIL: gcc.c-torture/compile/20000329-1.c, -O2
FAIL: gcc.c-torture/compile/20000329-1.c, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/compile/20000329-1.c, -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/compile/20000329-1.c, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/compile/20000329-1.c, -O3 -g
FAIL: gcc.c-torture/execute/20000225-1.c execution, -O2
FAIL: gcc.c-torture/execute/20000225-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/20000225-1.c execution, -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/20000225-1.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/20000225-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/20000225-1.c execution, -Os
FAIL: gcc.c-torture/execute/991221-1.c execution, -O1
FAIL: gcc.c-torture/execute/991221-1.c execution, -O2
FAIL: gcc.c-torture/execute/991221-1.c execution, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/991221-1.c execution, -O3 -g
FAIL: gcc.c-torture/execute/991221-1.c execution, -Os
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -O1
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -O2
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -O3 -fomit-frame-pointer
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -O3 -fomit-frame-pointer -funroll-loops
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -O3 -g
WARNING: program timed out.
FAIL: gcc.c-torture/execute/memcpy-1.c compilation, -Os
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O0
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O1
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O2
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O3 -fomit-frame-pointer -funroll-loops
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -O3 -g
FAIL: gcc.c-torture/execute/ieee/fp-cmp-4.c compilation, -Os
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -O1
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -O2
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -O3 -fomit-frame-pointer
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -O3 -fomit-frame-pointer -funroll-loops
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -O3 -g
WARNING: program timed out.
FAIL: gcc.c-torture/unsorted/memtst.c, -Os
FAIL: gcc.dg/990424-1.c execution test
FAIL: gcc.dg/991214-1.c (test for excess errors)
FAIL: gcc.dg/cpp-ifparen.c with paren (test for bogus messages, line 2)
FAIL: gcc.dg/cpp-redef-2.c anon varargs (test for warnings, line 15)
FAIL: gcc.dg/noreturn-1.c this function should not get any warnings (test for bogus messages, line 50)
FAIL: gcc.dg/noreturn-1.c detect return from tail call (test for warnings, line 57)
The memtest and memcpy failures are new - I'm not sure which else are
new.
The problem of excessive memory usage which I've reported has been
confirmed. cc1 uses sometimes more than 256 MB and can't be compiled
anymore on my notebook with 128 MB of RAM and 128 MB of swap (I
managed to do this before your changes went in).
My system: glibc 2.1.3, i686-linux.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
More information about the Gcc-patches
mailing list