From: Nick Clifton <nickc@redhat.com>
To: Christian Joensson <christian.joensson@gmail.com>
Cc: binutils@sources.redhat.com
Subject: Re: Quite some waring using gcc4... [Was: Results for 2.15.94 20041222 testsuite on i686-pc-linux-gnu]
Date: Thu, 23 Dec 2004 11:11:00 -0000 [thread overview]
Message-ID: <41CAA96D.3060609@redhat.com> (raw)
In-Reply-To: <20041222210936.GA23378@fw.j-son.org>
Hi Christian,
>>Number of warnings per file:
>> 34 /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
>> 8 /usr/local/src/trunk/src/bfd/merge.c
>> 6 /usr/local/src/trunk/src/ld/ldexp.c
>> 5 libiberty/concat.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
>> 3 libiberty/regex.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
>> 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
>> 1 libiberty/pex-unix.c
> Is this something someone wants more info about?
Yes please - one thing I would very much like to do is to be able to
build binutils with -Wall -Werror enabled.
Cheers
Nick
prev parent reply other threads:[~2004-12-23 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 21:08 Results for 2.15.94 20041222 testsuite on i686-pc-linux-gnu Christian Joensson
2004-12-22 21:09 ` Quite some waring using gcc4... [Was: Results for 2.15.94 20041222 testsuite on i686-pc-linux-gnu] Christian Joensson
2004-12-23 11:11 ` Nick Clifton [this message]
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=41CAA96D.3060609@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=christian.joensson@gmail.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).