From: Manoj Iyer <manjo@austin.ibm.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>,
gdb-patches@sources.redhat.com
Subject: Re: [commit] gdb_byte part of ppc
Date: Wed, 25 May 2005 23:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0505251001010.31147@lazy> (raw)
In-Reply-To: <429476B0.3010506@gnu.org>
I send out a similar patch for review yestarday and it covers a few more
files, any comments on that one? Would you like a similar patch for
sim/ppc files?
-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cogito ergo sum +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On Wed, 25 May 2005, Andrew Cagney wrote:
> M.M. Kettenis wrote:
> > Andrew Cagney <cagney@gnu.org> wrote:
> >
> >> these files, for the moment, get past gcc4
> >
> >
> > Great! Have you been able to test i386 with gcc4 lately?
>
> You can try. However, let me rephrase the above:
>
> These files, along with a few others, do get past gcc4 -Werror. Many
> don't, gdb_byte being just one problem. gcc4 -Werror continues to be
> pretty much useless.
>
> > I think I've
> > done most of the conversion, but I haven't been able to install gcc4 on
> > my systems yet, and I won't be able to do so until I'm back home.
> >
> > Anyway, I've seen a lot of breakage from -Werror lately. I really think
> > we should make that the default, at least for cvs version, after we've
> > fixed all the gdb_byte fallout. Otherwise this will never be fixed
> > proberly.
>
> Like binutils? Sounds like something for gdb@
>
next prev parent reply other threads:[~2005-05-25 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 5:37 Andrew Cagney
2005-05-25 6:09 ` M.M. Kettenis
2005-05-25 18:28 ` Andrew Cagney
2005-05-25 23:54 ` Manoj Iyer [this message]
2005-05-26 20:52 ` Andrew Cagney
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=Pine.LNX.4.58.0505251001010.31147@lazy \
--to=manjo@austin.ibm.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=m.m.kettenis@alumnus.utwente.nl \
/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