public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: manfred@s-direktnet.de
To: egcs@cygnus.com
Subject: egcs-971201: results on sparc-sun-solaris2.5.1 haifa disabled
Date: Tue, 02 Dec 1997 09:56:00 -0000	[thread overview]
Message-ID: <9712021126.AA23167@lts.sel.alcatel.de> (raw)

These are my results for egcs-971201 on sparc-sun-solaris2.5.1 using

  - GNU binutils-2.8.1	 (almost the official version)
  - plain egcs-971127 plus the following patches:

    [1]: [971016]: PICFLAG vs. multilib - solution from <manfred@s-direktnet.de>
    [2]: egcs-970929: GNU assembler too picky from <manfred@ks.sel.alcatel.de>
    [3]: Install c++filt from <manfred@s-direktnet.de>
    [4]: egcs-970929: Missing SHELL from <manfred@ks.sel.alcatel.de>
    [5]: [971031]: Fix for broken hypot funct. on m88k-motorola-sysv3
	 from <manfred@s-direktnet.de>
    [6]: `Re: 'make bootstrap' failure on  m88k-dg-dgux5.4R3.10' patch #2 from
	  <manfred@s-direktnet.de>
    [7]: class.c (prepare_fresh_vtable): Enable even more complex MI
	 vtable names patch from <mrs@wrs.com>


config env:
	CC=gcc CFLAGS='-O9' LDFLAGS='-s'
config flags:
	--enable-shared	--enable-threads				\
	--with-gnu-as --with-gnu-ld					\
	--prefix=/u/b60/manfred/gnu/sparc-sun-solaris2			\
	--with-gxx-include-dir=/u/b60/manfred/gnu/sparc-sun-solaris2/lib/gcc-lib/sparc-sun-solaris2.5.1/egcs-2.90.20/include/g++ \
	--with-local-prefix=/u/b60/manfred/gnu/sparc-sun-solaris2

BOOT_CFLAGS:
	-O9
gcc used for bootstrapping:
	gcc version egcs-2.90.19 971127 (gcc2-970802 experimental)


Test Run By manfred on Tue Dec  2 10:51:13 1997
Native configuration is sparc-sun-solaris2.5.1

		=== libio Summary ===

# of expected passes		40


Test Run By manfred on Tue Dec  2 10:52:36 1997
Native configuration is sparc-sun-solaris2.5.1

		=== libstdc++ Summary ===

# of expected passes		30


Test Run By manfred on Tue Dec  2 10:53:47 1997
Native configuration is sparc-sun-solaris2.5.1

		=== gcc tests ===

FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 

		=== gcc Summary ===

# of expected passes		4881
# of unexpected failures	4
# of expected failures		5
# of unsupported tests		6
/local/manfred/work/GNU/egcs-971201-sparc-sun-solaris2.5.1/gcc/xgcc version egcs-2.90.20 971201 (gcc2-970802 experimental)


Test Run By manfred on Tue Dec  2 11:44:33 1997
Native configuration is sparc-sun-solaris2.5.1

		=== g++ tests ===

XPASS: g++.mike/dyncast1.C  Execution test
XPASS: g++.mike/dyncast2.C  Execution test

		=== g++ Summary ===

# of expected passes		3400
# of unexpected successes	2
# of expected failures		79
# of untested testcases		6
/local/manfred/work/GNU/egcs-971201-sparc-sun-solaris2.5.1/gcc/testsuite/../xgcc version egcs-2.90.20 971201 (gcc2-970802 experimental)

             reply	other threads:[~1997-12-02  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-02  9:56 manfred [this message]
1997-12-02 13:14 ` Joe Buck
1997-12-03  3:30   ` Manfred.Hollstein
1997-12-03  3:30   ` Manfred.Hollstein
1997-12-03  4:08 manfred

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=9712021126.AA23167@lts.sel.alcatel.de \
    --to=manfred@s-direktnet.de \
    --cc=egcs@cygnus.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).