From: Christian Joensson <christian.joensson@gmail.com>
To: binutils <binutils@sources.redhat.com>
Subject: Results for 2.15.94 20050222 testsuite on sparc-unknown-linux-gnu
Date: Wed, 23 Feb 2005 11:38:00 -0000 [thread overview]
Message-ID: <20050223083148.GA736@ultra10.j-son.org> (raw)
Aurora SPARC Linux release 2.0 (Kashmir FC3) UltraSparc IIi (Sabre) sun4u:
binutils-2.15.92.0.2-5 - sparc
bison-1.875c-2 - sparc
dejagnu-1.4.4-2 - noarch
expect-5.42.1-1 - sparc
gcc-3.4.2-6.fc3 - sparc
gcc4-4.0.0-0.8sparc - sparc
glibc-2.3.3-99 - sparc64
glibc-2.3.3-99 - sparcv9
glibc-headers-2.3.3-99 - sparc64
glibc-kernheaders-2.6-20sparc - sparc
kernel-2.6.10-1.1110sparc18 - sparc64
package kernel-smp is not installed
make-3.80-5 - sparc
nptl-devel-2.3.3-99 - sparcv9
tcl-8.4.7-2 - sparc
LAST_UPDATED: Tue Feb 22 09:25:16 UTC 2005
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 88
=== ld tests ===
Running target unix
=== ld Summary ===
# of expected passes 238
# of expected failures 5
version: 2.15.94 20050222
Platform: sparc-unknown-linux-gnu
configure flags: sparc-linux --enable-__cxa_atexit --enable-shared --enable-build-warnings=-Wall,-Wstrict-prototypes,-Wmissing-prototypes --enable-64-bit-bfd
Counting all warnings,
there are 64 warnings in stage0 of this bootstrap.
Number of warnings per file:
14 /usr/local/src/trunk/src/binutils/readelf.c
10 /usr/local/src/trunk/src/binutils/bucomm.c
10 libiberty/concat.c
6 libiberty/regex.c
5 /usr/local/src/trunk/src/ld/ldexp.c
4 /usr/local/src/trunk/src/gprof/gmon_io.c
3 esun4.c
2 /usr/local/src/trunk/src/gprof/hist.c
2 libiberty/pex-unix.c
2 include/xregex2.h
1 /usr/local/src/trunk/src/ld/ldwrite.c
1 /usr/local/src/trunk/src/gprof/basic_blocks.c
1 /usr/local/src/trunk/src/gas/read.c
1 /usr/local/src/trunk/src/gas/config/obj-elf.c
1 /usr/local/src/trunk/src/binutils/objdump.c
1 /usr/local/src/trunk/src/bfd/elf.c
Number of warning types:
10 traditional C rejects ISO C style function definitions
10 the use of \`???' is dangerous, better use \`???'
10 pointer targets in assignment differ in signedness
6 signed and unsigned type in conditional expression
6 pointer targets in passing argument 2 of 'gmon_io_read_32' differ in signedness
5 pointer targets in passing argument 2 of 'read_leb128' differ in signedness
2 variable 'out' might be clobbered by 'longjmp' or 'vfork'
2 pointer targets in passing argument 1 of 'strcpy' differ in signedness
2 pointer targets in passing argument 1 of 'byte_get' differ in signedness
2 ISO C90 does not support 'static' or type qualifiers in parameter array declarators
1 'strtab' may be used uninitialized in this function
1 'result\$value' is used uninitialized in this function
1 'result\$valid_p' may be used uninitialized in this function
1 'result\$str' is used uninitialized in this function
1 'result\$section' is used uninitialized in this function
1 pointer targets in passing argument 2 of 'check_eh_frame' differ in signedness
1 pointer targets in passing argument 1 of 'strlen' differ in signedness
1 pointer targets in passing argument 1 of 'strchr' differ in signedness
1 'count' may be used uninitialized in this function
reply other threads:[~2005-02-23 8:32 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=20050223083148.GA736@ultra10.j-son.org \
--to=christian.joensson@gmail.com \
--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).