public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Christian Joensson <christian.joensson@gmail.com>
To: binutils <binutils@sources.redhat.com>
Subject: Results for 2.15.94 20050215 testsuite on i686-pc-linux-gnu
Date: Wed, 16 Feb 2005 02:37:00 -0000	[thread overview]
Message-ID: <5460e333050215103231856da8@mail.gmail.com> (raw)

Fedora Core release 3 (Heidelberg)  ia32 pentium II single i686:

binutils-2.15.92.0.2-5 - i386
bison-1.875c-2 - i386
dejagnu-1.4.4-2 - noarch
expect-5.42.1-1 - i386
gcc-3.4.2-6.fc3 - i386
gcc4-4.0.0-0.8 - i386
glibc-2.3.4-2.fc3 - i686
glibc-headers-2.3.4-2.fc3 - i386
glibc-kernheaders-2.4-9.1.87 - i386
kernel-2.6.10-1.760_FC3 - i686
package kernel-smp is not installed
make-3.80-5 - i386
nptl-devel-2.3.4-2.fc3 - i686
tcl-8.4.7-2 - i386

LAST_UPDATED: Tue Feb 15 18:01:27 UTC 2005

Native configuration is i686-pc-linux-gnu

		=== binutils tests ===


Running target unix

		=== binutils Summary ===

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


Running target unix

		=== gas Summary ===

# of expected passes		101
		=== ld tests ===


Running target unix

		=== ld Summary ===

# of expected passes		239
# of expected failures		4

version: 2.15.94 20050215
Platform: i686-pc-linux-gnu
configure flags: --enable-__cxa_atexit --enable-shared
--enable-build-warnings=-Wall,-Wstrict-prototypes,-Wmissing-prototypes
Counting all warnings,
there are 137 warnings in stage0 of this bootstrap.

Number of warnings per file:
     26 /usr/local/src/trunk/src/bfd/elf-eh-frame.c
     22 /usr/local/src/trunk/src/bfd/peicode.h
     14 /usr/local/src/trunk/src/binutils/readelf.c
     10 /usr/local/src/trunk/src/binutils/bucomm.c
     10 libiberty/concat.c
      8 /usr/local/src/trunk/src/bfd/merge.c
      6 /usr/local/src/trunk/src/ld/ldexp.c
      6 libiberty/regex.c
      4 /usr/local/src/trunk/src/gprof/gmon_io.c
      4 /usr/local/src/trunk/src/bfd/opncls.c
      4 /usr/local/src/trunk/src/bfd/elf.c
      3 /usr/local/src/trunk/src/bfd/dwarf2.c
      2 /usr/local/src/trunk/src/gprof/hist.c
      2 /usr/local/src/trunk/src/bfd/srec.c
      2 /usr/local/src/trunk/src/bfd/elf-strtab.c
      2 /usr/local/src/trunk/src/bfd/cofflink.c
      2 /usr/local/src/trunk/src/bfd/coffgen.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/elfcode.h

Number of warning types:
     25 pointer targets in assignment differ in signedness
     20 pointer targets in passing argument 1 of 'strlen' differ in signedness
     10 traditional C rejects ISO C style function definitions
     10 the use of \`???' is dangerous, better use \`???'
      8 pointer targets in passing argument 1 of '__builtin_strcmp'
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
      6 pointer targets in initialization differ in signedness
      5 pointer targets in passing argument 2 of 'read_leb128' differ
in signedness
      4 pointer targets in passing argument 2 of '__builtin_strcmp'
differ in signedness
      3 pointer targets in passing argument 3 of
'pe_ILF_make_a_symbol' differ in signedness
      3 pointer targets in passing argument 2 of 'sec_merge_add'
differ in signedness
      3 pointer targets in passing argument 1 of '__builtin_strchr'
differ in signedness
      2 variable 'out' might be clobbered by 'longjmp' or 'vfork'
      2 pointer targets in passing argument 2 of
'bfd_calc_gnu_debuglink_crc32' differ in signedness
      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 return differ in signedness
      1 pointer targets in passing argument 5 of 'srec_write_record'
differ in signedness
      1 pointer targets in passing argument 4 of 'srec_write_record'
differ in signedness
      1 pointer targets in passing argument 3 of
'coff_write_native_symbol' differ in signedness
      1 pointer targets in passing argument 3 of
'coff_write_alien_symbol' differ in signedness
      1 pointer targets in passing argument 3 of
'bfd_simple_get_relocated_section_contents' differ in signedness
      1 pointer targets in passing argument 2 of 'strcpy' differ in signedness
      1 pointer targets in passing argument 2 of
'sec_merge_hash_lookup' differ in signedness
      1 pointer targets in passing argument 2 of 'check_eh_frame'
differ in signedness
      1 pointer targets in passing argument 1 of 'strrchr' differ in signedness
      1 'new\$str' is used uninitialized in this function
      1 'hdr\$length' may be used uninitialized in this function
      1 'count' may be used uninitialized in this function

                 reply	other threads:[~2005-02-15 18: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=5460e333050215103231856da8@mail.gmail.com \
    --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).