public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Christian Joensson <christian@j-son.org>
To: binutils <binutils@sources.redhat.com>
Subject: Results for 2.15.94 20041109 testsuite on sparc-unknown-linux-gnu
Date: Tue, 09 Nov 2004 08:35:00 -0000	[thread overview]
Message-ID: <20041109083538.GA27273@fw.j-son.org> (raw)

Aurora SPARC Linux release 1.92 (Tangerine FC2) UltraSparc IIi (Sabre) sun4u:

binutils-2.15.90.0.3-6
bison-1.875-7.1
dejagnu-1.4.2-11
expect-5.39.0-96.1
gcc-3.3.4-2
glibc-2.3.3-27
glibc-headers-2.3.3-27
glibc-kernheaders-2.6-16sparc
kernel-2.6.8-1.571sp1
tcl-8.4.5-7

LAST_UPDATED: Tue Nov  9 07:55:17 UTC 2004

Native configuration is sparc-unknown-linux-gnu

		=== binutils tests ===


Running target unix

		=== binutils Summary ===

# of expected passes		33
		=== gas tests ===


Running target unix

		=== gas Summary ===

# of expected passes		69
		=== ld tests ===


Running target unix
FAIL: vers2
FAIL: vers26b1
FAIL: vers26b2
FAIL: vers26b3
FAIL: TLS -fno-pic -shared

		=== ld Summary ===

# of expected passes		228
# of unexpected failures	5
# of expected failures		3

version: 2.15.94 20041109
Platform: sparc-unknown-linux-gnu
configure flags: --enable-__cxa_atexit --enable-shared
Counting all warnings,
there are 23 warnings in stage0 of this bootstrap.

Number of warnings per file:
     10 /usr/local/src/trunk/src/binutils/bucomm.c
      6 libiberty/regex.c
      4 include/fibheap.h
      2 include/xregex2.h
      1 lex.yy.c

Number of warning types:
     10 the use of \`???' is dangerous, better use \`???'
      6 signed and unsigned type in conditional expression
      4 bit-field \`???' type invalid in ISO C
      2 ISO C90 does not support \`static' or type qualifiers in parameter array declarators
      1 \`???' defined but not used

                 reply	other threads:[~2004-11-09  8:35 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=20041109083538.GA27273@fw.j-son.org \
    --to=christian@j-son.org \
    --cc=binutils@sources.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).