From: Christian Joensson <christian.joensson@gmail.com>
To: binutils <binutils@sources.redhat.com>
Subject: Results for 2.15.94 20050215 testsuite on i686-pc-cygwin
Date: Wed, 16 Feb 2005 01:50:00 -0000 [thread overview]
Message-ID: <5460e33305021510294569ee3a@mail.gmail.com> (raw)
Windows XP/SP2 cygwin ia32 pentium III dual i686:
binutils 20041229-1 2.15.94 20041229
bison 20030307-1 1.875b
cygwin 1.5.12-1
dejagnu 20021217-2 1.4.2.x
expect 20030128-1 5.26
gcc 3.3.3-3
make 3.80-1
LAST_UPDATED: Tue Feb 15 17:59:15 UTC 2005
Native configuration is i686-pc-cygwin
=== binutils tests ===
Running target unix
=== binutils Summary ===
# of expected passes 71
# of expected failures 1
=== gas tests ===
Running target unix
=== gas Summary ===
# of expected passes 69
=== ld tests ===
Running target unix
FAIL: cdtest with -Ur
FAIL: weak symbols
=== ld Summary ===
# of expected passes 36
# of unexpected failures 2
# of expected failures 3
version: 2.15.94 20050215
Platform: i686-pc-cygwin
configure flags: --enable-__cxa_atexit --enable-shared
--enable-build-warnings=-Wall,-Wstrict-prototypes,-Wmissing-prototypes
Counting all warnings,
there are 16 warnings in stage0 of this bootstrap.
Number of warnings per file:
3 libiberty/regex.c
3 include/getopt.h
2 libiberty/getopt.c
2 lex.yy.c
2 /usr/local/src/trunk/src/bfd/elf.c
1 libtool
1 libiberty/strsignal.c
1 include/xregex2.h
1 /usr/local/src/trunk/src/intl/l10nflist.c
Number of warning types:
3 signed and unsigned type in conditional expression
3 function declaration isn't a prototype
2 unused parameter \`???'
2 \`???' defined but not used
2 ??? format, ??? arg (arg ???)
1 comparison between signed and unsigned
1 assignment makes pointer from integer without a cast
1 \`???' seems to be moved
1 ISO C90 does not support \`static' or type qualifiers in
parameter array declarators
reply other threads:[~2005-02-15 18:29 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=5460e33305021510294569ee3a@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).