From: Andrew Cagney <cagney@gnu.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>,
gdb-patches@sources.redhat.com
Subject: Re: [commit] gdb_byte part of ppc
Date: Thu, 26 May 2005 20:52:00 -0000 [thread overview]
Message-ID: <4295E8AA.7000700@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0505251001010.31147@lazy>
Manoj Iyer wrote:
> I send out a similar patch for review yestarday and it covers a few more
> files, any comments on that one?
Oops :-( If you look carefully through what I committed you'll notice:
rs6000_fetch_pointer_argument (struct frame_info *frame, int argi,
struct type *type)
{
- CORE_ADDR addr;
- get_frame_register (frame, 3 + argi, &addr);
- return addr;
+ return get_frame_register_unsigned (frame, 3 + argi);
}
See the problem? I don't seem to be able to find that change in your
patch which puzzles me. With the combination of gcc4, gdb_byte, and
-Werror I couldn't miss it.
Can I suggest installing gcc4 and then using that to build gdb
(configured with --enable-gdb-warnings=,-Werror) and look at the
problems identified (you can override -Werror forcing a successful build
using `cd ...build/gdb && make WERROR_CFLAGS=` )? Warning fixes to
*ppc* files identified doing that are fairly obvious (I keep finding the
need to make related changes).
That leaves the s/unsigned char/gdb_byte/, that is probably also obvious
(assuming it isn't leaving warnings behind).
prev parent reply other threads:[~2005-05-26 15:24 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
2005-05-26 20:52 ` Andrew Cagney [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=4295E8AA.7000700@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=m.m.kettenis@alumnus.utwente.nl \
--cc=manjo@austin.ibm.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