public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: egcs@cygnus.com
Cc: Geoffrey KEATING <geoffk@discus.anu.edu.au>,
	Elliot Lee <sopwith@redhat.com>,
	Michael Meissner <meissner@cygnus.com>,
	Gary Thomas <g.thomas@opengroup.org>
Subject: egcs-971114: results on powerpc-unknown-linux-gnulibc1
Date: Sun, 16 Nov 1997 15:47:00 -0000	[thread overview]
Message-ID: <v03110701b0954942c8ea@[195.180.235.96]> (raw)

Hi,

I did run the tests with the following patches installed:
< http://homepages.munich.netsurf.de/Franz.Sirl/misc/ppclibc1.diff >
< http://homepages.munich.netsurf.de/Franz.Sirl/misc/egcs-971105-geoffk.diff >
< http://homepages.munich.netsurf.de/Franz.Sirl/misc/egcs-971105-geoffk2.diff >
and H.J.Lu's patch for configure.in to support libg++.

on a Linux/PPC system with:
binutils-2.8.0.17 (compiled with egcs-971105)
glibc-961212 (1.99 alpha)

Without Geoff's patches I get around 50 more unexpected fails during g++,
gcc remains unchanged. Most FAILs of gcc seem to be related to trampolines.
During gcc.c-torture/special/920520-1.c the compiler (cc1) segfaults, so
how can I debug cc1 with gdb?

Compiling glibc-971112 passes posix/glob.c with -O2 and
linuxthreads/condvars.c with -O1, I haven't tested condvars.c with -O2 yet
(used to throw "forbidden register spilled" with egcs-971105). Testing the
resulting libs usually gives:
BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 63: elf_get_dynamic_info:
Assertion `info[9]->d_un.d_val == sizeof (Elf32_Rela)' failed!

If I comment out the offending assert, I usually get "Symbol not found" or
"ELF_PPC_REL24 relocation out of range". The last one usually happens if
libtermcap.so is involved.

Bye,
Franz.


Test Run By root on Sun Nov 16 16:34:54 1997
Native configuration is powerpc-unknown-linux-gnulibc1

                === gcc tests ===

FAIL: gcc.c-torture/execute/921215-1.c execution,  -O0
FAIL: gcc.c-torture/execute/921215-1.c execution,  -O1
FAIL: gcc.c-torture/execute/921215-1.c execution,  -O2
FAIL: gcc.c-torture/execute/921215-1.c execution,  -O2 -fomit-frame-pointer
-finline-functions
FAIL: gcc.c-torture/execute/931002-1.c execution,  -O0
FAIL: gcc.c-torture/execute/931002-1.c execution,  -O1
FAIL: gcc.c-torture/execute/931002-1.c execution,  -O2
FAIL: gcc.c-torture/execute/931002-1.c execution,  -O2 -fomit-frame-pointer
-finline-functions
FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2
-fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/nestfunc-1.c execution,  -O0
FAIL: gcc.c-torture/execute/nestfunc-1.c execution,  -O1
FAIL: gcc.c-torture/execute/nestfunc-1.c execution,  -O2
FAIL: gcc.c-torture/execute/nestfunc-1.c execution,  -O2
-fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/special/920520-1.c,  -O0  -S
FAIL: gcc.c-torture/special/920520-1.c,  -O1  -S
FAIL: gcc.c-torture/special/920520-1.c,  -O2  -S
FAIL: gcc.c-torture/special/920520-1.c,  -O2 -fomit-frame-pointer
-finline-functions  -S
UNSUPPORTED: gcc.dg/bf-spl1.c
UNSUPPORTED: gcc.dg/dll-1.c
UNSUPPORTED: gcc.dg/dll-2.c
UNSUPPORTED: gcc.dg/dll-3.c
UNSUPPORTED: gcc.dg/dll-4.c
UNSUPPORTED: gcc.dg/splet-1.c
UNSUPPORTED: gcc.dg/struct-ret-1.c

                === gcc Summary ===

# of expected passes            4866
# of unexpected failures        17
# of expected failures          5
# of unsupported tests          7
/usr/src/e/b-egcs-971114-2/gcc/xgcc version egcs-2.90.17 971114
(gcc2-970802 experimental)


Test Run By root on Sun Nov 16 17:40:17 1997
Native configuration is powerpc-unknown-linux-gnulibc1

                === g++ tests ===

Running /usr/src/e/egcs/gcc/testsuite/g++.old-deja/old-deja.exp ...
FAIL: g++.benjamin/warn01.C (test for excess errors)
FAIL: g++.brendan/template9.C  Execution test
FAIL: g++.jason/2371.C  Execution test
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
FAIL: g++.jason/new2.C (test for excess errors)
FAIL: g++.jason/template24.C  Execution test
FAIL: g++.jason/thunk3.C (test for excess errors)
FAIL: g++.jason/typeid1.C  Execution test
FAIL: g++.law/arg8.C  Execution test
FAIL: g++.law/profile1.C  Execution test
FAIL: g++.law/virtual3.C  Execution test
XPASS: g++.mike/dyncast1.C  Execution test
XPASS: g++.mike/dyncast2.C  Execution test
FAIL: g++.mike/eh2.C  Execution test
FAIL: g++.mike/p6610a.C  Execution test

                === g++ Summary ===

# of expected passes            3367
# of unexpected failures        12
# of unexpected successes       3
# of expected failures          81
# of untested testcases         6
/usr/src/e/b-egcs-971114-2/gcc/testsuite/../xgcc version egcs-2.90.17
971114 (gcc2-970802 experimental)





                 reply	other threads:[~1997-11-16 15:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='v03110701b0954942c8ea@[195.180.235.96]' \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=egcs@cygnus.com \
    --cc=g.thomas@opengroup.org \
    --cc=geoffk@discus.anu.edu.au \
    --cc=meissner@cygnus.com \
    --cc=sopwith@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).