From: Pedro Alves <palves@redhat.com>
To: selven <pcthegreat@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Redeclaration of regcache_register_status differs from previous declaration
Date: Fri, 28 Sep 2012 12:05:00 -0000 [thread overview]
Message-ID: <5065928C.2080805@redhat.com> (raw)
In-Reply-To: <CADW03iqgC=8e2XEsQfnSiuHNiKHhXzCOaY2naCOaF6wzDN94NA@mail.gmail.com>
On 09/28/2012 12:27 PM, selven wrote:
> Hi, I've never submitted a patch to gdb before, I don't know how to do
> this,
See <http://sourceware.org/gdb/contribute/>.
> and I searched the wiki couldn't find more info.
Yeah, we certainly could do better here.
> I was trying to compile gdb on aix
> Currently:
> gdb/regcache.c
> 414 int
> 415 regcache_register_status (const struct regcache *regcache, int regnum)
>
> Definition in regcache.h:
> gdb/regcache.h
> 66 enum register_status regcache_register_status (const struct
> regcache *regcache,
> 67 int regnum);
>
>
> Should be:
> 414 enum register_status
> 415 regcache_register_status (const struct regcache *regcache, int regnum)
Whoops.
>
> (So i kinda decided to post a patch, which sounded awesome :p )
It is. :-) The AIX port is in need of TLC (particularly to adapt
it to modern interfaces). It would be great of someone stepped up
to give it some. ;-)
I've applied this for you.
Thanks!
2012-09-28 selven <pcthegreat@gmail.com>
Make definition match declaration.
* regcache.c (regcache_register_status): Change return type to
enum register_status.
---
gdb/regcache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/regcache.c b/gdb/regcache.c
index c716280..449f682 100644
--- a/gdb/regcache.c
+++ b/gdb/regcache.c
@@ -411,7 +411,7 @@ regcache_dup (struct regcache *src)
return newbuf;
}
-int
+enum register_status
regcache_register_status (const struct regcache *regcache, int regnum)
{
gdb_assert (regcache != NULL);
prev parent reply other threads:[~2012-09-28 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 11:27 selven
2012-09-28 12:05 ` Pedro Alves [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=5065928C.2080805@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pcthegreat@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